summaryrefslogtreecommitdiff
path: root/configure.ac
Commit message (Collapse)AuthorAgeFilesLines
* main: Also support CLI extensions in `/usr/libexec/libostree/ext`Colin Walters2022-01-111-0/+4
| | | | | | | | | | | | | In fixing https://github.com/coreos/rpm-ostree/pull/3323 I felt that it was a bit ugly we're installing `/usr/bin/ostree-container`. It's kind of an implementation detail. We want users to use `ostree container`. Let's support values outside of $PATH too. For example, this also ensures that TAB completion for `ost` expands to `ostree ` with a space.
* configure: post-release version bumprelease-2022.1Luca BRUNO2022-01-051-2/+2
|
* Release 2022.1v2022.1Luca BRUNO2022-01-051-3/+3
|
* rofiles-fuse: Build using FUSE 3 if possible, falling back to FUSE 2Simon McVittie2022-01-041-2/+17
| | | | | | | | This adds build-time configuration logic to automatically detect and switch between libfuse 2.x and 3.x. Signed-off-by: Simon McVittie <smcv@collabora.com> Co-authored-by: Luca BRUNO <luca.bruno@coreos.com>
* configure: post-release version bumprelease-2021.6Luca BRUNO2021-11-231-2/+2
|
* Release 2021.6v2021.6Luca BRUNO2021-11-231-1/+1
|
* configure: post-release version bumprelease-2021.5Colin Walters2021-10-051-2/+2
|
* Release 2021.5v2021.5Colin Walters2021-10-051-1/+1
|
* configure: post-release version bumpColin Walters2021-09-081-2/+2
|
* Release 2021.4Colin Walters2021-09-081-1/+1
|
* configure: post-release version bumpLuca BRUNO2021-07-121-2/+2
|
* Release 2021.3v2021.3Luca BRUNO2021-07-121-1/+1
|
* Use generator to enable ostree-remount.service and ostree-finalize-staged.pathColin Walters2021-06-161-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | We struggled for a long time with enablement of our "internal units", trying to follow the philosophy that units should only be enabled by explicit preset. See https://bugzilla.redhat.com/show_bug.cgi?id=1451458 and https://github.com/coreos/rpm-ostree/pull/1482 etc. And I just saw chat (RH internal on a proprietary system sadly) where someone hit `ostree-remount.service` not being enabled in CentOS8. Thinking about this more, I realized we've shipped a systemd generator for a long time and while its only role until now was to generate `var.mount`, but by using it to force on our internal units, we don't require people to deal with presets anymore. Basically we're inverting things so that "if ostree= is on the kernel cmdline, then enable our units" and not "enable our units, but have them use ConditionKernelCmdline=ostree to skip". Drop the weird gyrations we were doing around `ostree-finalize-staged.path` too; forking `systemctl start` is just asking for bugs. So after this, hopefully we won't ever again have to think about distribution presets and our units.
* build-sys: Bump required GLib to 2.44Dan Nicholson2021-06-051-1/+1
| | | | | | | | | | | | This will allow usage of `GMutexLocker`. This should be available on many older distros: * RHEL 7 - 2.56.1 * RHEL 8 - 2.56.4 * Debian 9 stretch (oldstable) - 2.50.3 * Debian 10 buster (stable) - 2.58.3 * Ubuntu 16.04 xenial - 2.48.2 * Ubuntu 18.04 bionic - 2.56.4
* configure: post-release version bumpColin Walters2021-04-151-2/+2
|
* Release 2021.2v2021.2Colin Walters2021-04-151-1/+1
|
* build-sys: Remove --enable-experimental-apiColin Walters2021-04-071-17/+1
| | | | | | | | | It was added for the collections bits, but we made that stable. It's now just cruft and we're very unlikely to reuse the infrastructure again. Motivated by a unit test failure when running from a tarball: https://github.com/ostreedev/ostree/issues/2313
* configure: post-release version bumpColin Walters2021-03-231-2/+2
|
* Release 2021.1v2021.1Colin Walters2021-03-231-3/+3
|
* Merge pull request #2306 from cgwalters/drop-core-rustJonathan Lebon2021-03-221-34/+0
|\
| * Drop minimal rust/ libraryColin Walters2021-03-181-34/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This was my first experiment with using Rust in this way; I gained a lot of knowledge from it. But, we don't really gain anything from the code as it is today - while it is "bit fiddling" code, the C code is well tested. We have a lot of compile-time options, and trimming them will be helpful. We've also gotten pushback on hard requiring Rust client side. Instead, what I'd like to do is hopefully soon create an `ostree-system` crate that uses the existing `ostree` library and can contain code drained from the rpm-ostree Rust and used by other projects perhaps. So the goal here is really more Rust, but we need to focus our efforts on where it's most valuable.
* | Add configure option for unsuffixed GRUB2 commandsKenneth J. Miller2021-03-181-0/+8
|/ | | | | | | | | | | | | | GRUB starting with version 2.02 permits the use of the linux and initrd commands for both EFI boot in *-efi installations, as well as 32-bit BIOS boot in i386-pc installations. This makes the use of the -16 and -efi suffixes for BIOS and EFI boot obsolete on systems with a modern GRUB installation. The --with-modern-grub configure flag makes ostree use the unsuffixed linux/initrd commands when generating a GRUB configuration, while defaulting to the previous behaviour for users not wanted this option.
* Add --enable-sanitizers, fix `make check` with itColin Walters2021-02-031-10/+11
| | | | | | | | It's cleaner if this is an build option rather than being kludged into the CI layer. Notably we can't use `LD_PRELOAD` anymore with ASAN, so update our tests to check for `ASAN_OPTIONS`.
* templates: add release-checklistLuca BRUNO2020-11-181-7/+1
| | | | This collects all release steps in a release-checklist template.
* configure: post-release version bumpLuca BRUNO2020-11-171-2/+2
|
* Release 2020.8v2020.8Luca BRUNO2020-11-171-1/+1
|
* Post-release version bumpColin Walters2020-10-131-2/+2
|
* Release 2020.7v2020.7Colin Walters2020-10-131-1/+1
|
* Avoid shadowing local variablesavoid-shadowsPhaedrus Leeds2020-09-131-0/+1
| | | | | | This should help with code readability. Fixes https://github.com/ostreedev/ostree/issues/2194
* Post-release version bumpColin Walters2020-09-031-2/+2
|
* Release 2020.6v2020.6Colin Walters2020-09-031-1/+1
| | | | Let's get the /var mount fix out at least.
* configure.ac: Set is_release_build=noJonathan Lebon2020-08-241-1/+1
| | | | We missed this during the post-release version bump.
* Post-release version bumpColin Walters2020-08-181-1/+1
|
* Release 2020.5v2020.5Colin Walters2020-08-181-1/+1
| | | | Mainly to get https://github.com/ostreedev/ostree/pull/2160 out.
* Post-release version bumpColin Walters2020-07-221-2/+2
|
* Release 2020.4v2020.4Colin Walters2020-07-211-1/+1
| | | | | A lot of stuff here, new signing API is the biggest. Let's get a release out.
* sign: rename option for enabling ed25519Denis Pynkin2020-04-171-6/+6
| | | | | | | | | | Use option `--with-ed25519-libsodium` instead of `--with-libsodium` to enable ed25519 signature engine. This allows to use later different implementations of ed25519 signing/verification. For instance, based on openssl. Signed-off-by: Denis Pynkin <denis.pynkin@collabora.com>
* Use `sign-ed25519` for the feature nameColin Walters2020-04-161-1/+1
| | | | | | | | `libsodium` is an implementation detail. In particular, I'd like to consider using OpenSSL for ed25519 (if libsodium isn't configured and openssl is). So switch the name of the exposed feature and adjust the tests.
* build-sys: Print libsodium status at end of configureColin Walters2020-03-251-0/+1
| | | | Like we do with other features.
* Add libsodium dependencyDenis Pynkin2020-03-251-0/+15
| | | | | | Allow to configure with libsodium flag. Signed-off-by: Denis Pynkin <denis.pynkin@collabora.com>
* Post-release version bumpJonathan Lebon2020-03-131-3/+3
|
* Release 2020.3v2020.3Jonathan Lebon2020-03-131-1/+1
| | | | | Let's do another release to get the `sysroot.readonly` fixes into FCOS and unpin ostree and rpm-ostree there.
* Post-release version bumpColin Walters2020-02-211-2/+2
|
* Release 2020.2v2020.2Colin Walters2020-02-211-2/+2
| | | | | | "Brown paper bag" release that actually sets the `is_release_build=yes` flag and also fixes the `Since:` on a few new functions.
* Post-release version bumpColin Walters2020-02-201-2/+2
|
* Release 2020.1v2020.1Colin Walters2020-02-201-3/+3
| | | | New year, new release!
* Initial fs-verity supportColin Walters2020-01-271-0/+5
| | | | | | | | | | | | | | | | | | Using fs-verity is natural for OSTree because it's file-based, as opposed to block based (like dm-verity). This only covers files - not symlinks or directories. And we clearly need to have integrity for the deployment directories at least. Also, what we likely need is an API that supports signing files as they're committed. So making this truly secure would need a lot more work. Nevertheless, I think it's time to start experimenting with it. Among other things, it does *finally* add an API that makes files immutable, which will help against some accidental damage. This is basic enablement work that is being driven by Fedora CoreOS; see also https://github.com/coreos/coreos-assembler/pull/876
* build: fix systemd feature advertisementAlex Kiernan2020-01-251-7/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 17db0f15a798 ("configure: add option for libsystemd") exposed --without-libsystemd to allow systemd to be disabled even if the systemd pkgconfig script was present, introducing a new variable with_libsystemd; there are now three, almost identical variables: - with_libsystemd [yes, no, maybe] - controlled by --without-libsystemd, resolved into yes/no by the initial checks - have_libsystemd [yes, no, <undefined>] - only set if with_libsystemd is yes/maybe, otherwise undefined - with_systemd [yes, <undefined>] - yes if have_systemd is yes, otherwise undefined with_systemd is the earliest variable and was previously set by a set of checks for dracut and mkinitcpio. These checks were changed for a systemd check in 9e2763106be0 ("lib: Use sd_journal directly (optionally)"). This commit also introduced BUILDOPT_LIBSYSTEMD, which will always match BUILDOPT_SYSTEMD. Fix the confusion by removing with_systemd which will always be yes when with_libsystemd=yes, or undefined if with_libsystemd=no. We can ignore the with_libsystemd=maybe case because it will always be resolved into yes/no before with_systemd is set. And replace all uses of BUILDOPT_SYSTEMD with BUILDOPT_LIBSYSTEMD, since they again always match. This fixes both the advertised features and the summary output when systemd is disabled by using with_libsystemd which is always defined. Signed-off-by: Alex Kiernan <alex.kiernan@gmail.com> Fixes: 5c62a7e4d0a5 ("build: Expose systemd in OSTREE_FEATURES") Fixes: 17db0f15a798 ("configure: add option for libsystemd") Supersedes: #1992
* build: Expose systemd in OSTREE_FEATURESAlex Kiernan2019-12-291-0/+1
| | | | Signed-off-by: Alex Kiernan <alex.kiernan@gmail.com>
* Post-release version bumpColin Walters2019-12-091-2/+2
|
View Lorry Controller Status