shaba/ostree
1
0
Fork 0
mirror of https://github.com/ostreedev/ostree.git synced 2024-10-26 08:55:19 +03:00
Code Issues Projects Releases Wiki Activity
8a9f067d61
ostree/Makefile-libostree.am

305 lines
11 KiB
Plaintext
Raw Normal View History

De-recursify source tree
2011-11-02 23:45:32 +04:00
# Makefile for C source code
#
pull: Add tls-client-cert-{path,key} (if we have new enough libsoup) This is an actually working version of client-side certificates. Depends on: See: https://bugzilla.gnome.org/show_bug.cgi?id=334021 We detect whether libsoup is new enough for this. https://bugzilla.gnome.org/show_bug.cgi?id=729356
2014-05-01 20:55:13 +04:00
# Copyright (C) 2011,2014 Colin Walters <walters@verbum.org>
De-recursify source tree
2011-11-02 23:45:32 +04:00
#
Add SPDX-License-Identifier to source files SPDX License List is a list of (common) open source licenses that can be referred to by a “short identifier”. It has several advantages compared to the common "license header texts" usually found in source files. Some of the advantages: * It is precise; there is no ambiguity due to variations in license header text * It is language neutral * It is easy to machine process * It is concise * It is simple and can be used without much cost in interpreted environments like java Script, etc. * An SPDX license identifier is immutable. * It provides simple guidance for developers who want to make sure the license for their code is respected See http://spdx.org for further reading. Signed-off-by: Marcus Folkesson <marcus.folkesson@gmail.com> Closes: #1439 Approved by: cgwalters
2018-01-30 22:26:26 +03:00
# SPDX-License-Identifier: LGPL-2.0+
#
Switch to LGPLv2+ for most code Since we're making a shared library, it should be usable by non-GPL apps. To allow more code sharing between the core and the tests, move them to the LGPLv2+ too. A few bits of test and other code are still GPL. See the new COPYING file for more information.
2011-11-10 22:17:04 +04:00
# This library is free software; you can redistribute it and/or
# modify it under the terms of the GNU Lesser General Public
# License as published by the Free Software Foundation; either
# version 2 of the License, or (at your option) any later version.
De-recursify source tree
2011-11-02 23:45:32 +04:00
#
Switch to LGPLv2+ for most code Since we're making a shared library, it should be usable by non-GPL apps. To allow more code sharing between the core and the tests, move them to the LGPLv2+ too. A few bits of test and other code are still GPL. See the new COPYING file for more information.
2011-11-10 22:17:04 +04:00
# This library is distributed in the hope that it will be useful,
De-recursify source tree
2011-11-02 23:45:32 +04:00
# but WITHOUT ANY WARRANTY; without even the implied warranty of
Switch to LGPLv2+ for most code Since we're making a shared library, it should be usable by non-GPL apps. To allow more code sharing between the core and the tests, move them to the LGPLv2+ too. A few bits of test and other code are still GPL. See the new COPYING file for more information.
2011-11-10 22:17:04 +04:00
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# Lesser General Public License for more details.
De-recursify source tree
2011-11-02 23:45:32 +04:00
#
Switch to LGPLv2+ for most code Since we're making a shared library, it should be usable by non-GPL apps. To allow more code sharing between the core and the tests, move them to the LGPLv2+ too. A few bits of test and other code are still GPL. See the new COPYING file for more information.
2011-11-10 22:17:04 +04:00
# You should have received a copy of the GNU Lesser General Public
Update FSF license notices to use URL instead of address
2021-12-07 04:20:55 +03:00
# License along with this library. If not, see <https://www.gnu.org/licenses/>.
De-recursify source tree
2011-11-02 23:45:32 +04:00
Add gtk-doc support Yes, it's really me. Colin Walters. Writing documentation. You don't need to do a DNA test.
2013-08-17 06:54:35 +04:00
include Makefile-libostree-defines.am
oxidation: Add implementation of bupsplit in Rust This is an initial drop of "oxidation", or adding implementation of components in Rust. The bupsplit code is a good target - no dependencies, just computation. Translation into Rust had a few twists - - The C code relies a lot on overflowing unsigned ints, and also on the C promotion rules for e.g. `uint8_t -> int32_t` - There were some odd loops that I introduced bugs in while translating...in particular, the function always returns `len`, but I mistakenly translated to `len+1`, resulting in an OOB read on the C side, which was hard to debug. On the plus side, an off-by-one array indexing in the Rust code paniced nicely. In practice, we'll need a lot more build infrastructure to make this work, such as using `cargo vendor` when producing build artifacts for example. Also, Cargo is yet another thing we need to cache. Where do we go with this? Well, I think we should merge this, it's not a lot of code. We can just have it be an alternative CI target. Should we do a lot more right now? Probably not immediately, but I find the medium/long term prospects pretty exciting! Closes: #656 Approved by: jlebon
2017-01-25 05:43:53 +03:00
bupsplitpath = libbupsplit.la
noinst_LTLIBRARIES += libbupsplit.la
libbupsplit_la_SOURCES = src/libostree/bupsplit.h src/libostree/bupsplit.c
deploy: Rework kernel arguments, add --karg-append to "admin deploy" The "ordered hash" code was really just for kernel arguments. And it turns out it needs to be a multihash (for e.g. multiple console= arguments). So turn the OstreeOrderedHash into OstreeKernelArgs, and move the bits to split key=value and such into there. Now we're not making this public API yet - the public OstreeSysroot just takes char **kargs. To facilitate code reuse between ostree/ and libostree/, make it a noinst libtool library. It'll be duplicated in the binary and library, but that's OK for now. We can investigate making OstreeKernelArgs public later. https://bugzilla.gnome.org/show_bug.cgi?id=721136
2014-01-16 22:04:00 +04:00
Install a shared library This required a fair bit of surgery because previously ostree.h included otutil.h, but that's supposed to be a private library.
2013-07-27 03:25:07 +04:00
lib_LTLIBRARIES += libostree-1.la
De-recursify source tree
2011-11-02 23:45:32 +04:00
Fix make distcheck make distcheck was unhappy for various reasons: * headers aren't data, so use _HEADERS otherwise compilation fails * Mark the gir & typelib data as cleanfiles so they aren't left around after make clean * Don't nuke the .la file. This breaks make uninstall, leave it up to distributions to not install .la files if they don't want them. https://bugzilla.gnome.org/show_bug.cgi?id=705850
2013-08-12 18:27:42 +04:00
libostreeincludedir = $(includedir)/ostree-1
libostree: add versioning macros OSTree currently provides no way to inspect the versioning information at run time, being only available at compile time through pkg-config. This is a problem for e.g. Flatpak, that needs to check whether the 'update-frequency' option is available. Checking at compile time isn't great since it's not looking for new symbols, but only if an optional feature is present. This commit, then, adds a new header that is generated at compile time, exposing OSTree's versioning information. Closes: #728 Approved by: cgwalters
2017-03-10 20:33:52 +03:00
libostreeinclude_HEADERS = $(libostree_public_headers) $(libostree_public_built_headers)
Install a shared library This required a fair bit of surgery because previously ostree.h included otutil.h, but that's supposed to be a private library.
2013-07-27 03:25:07 +04:00
build: Don't run glib-mkenums if there's nothing to do This fixes the build without libsoup. Closes: #296 Approved by: gatispaeglis
2016-05-12 17:15:24 +03:00
ENUM_TYPES = $(NULL)
ENUM_TYPES += $(srcdir)/src/libostree/ostree-fetcher.h
fetcher: Add "config-flags" construct-only property A lot of effort here just to avoid touching SoupSession directly in ostree_fetcher_new(). The reason will become apparent in subsequent commits. Note this introduces generated enum/flags GTypes using glib-mkenums. I could have just made the property type as plain integer, but doing properties right will henceforth be easier now that the automake-fu is established.
2015-11-10 03:04:42 +03:00
build: Add a TODO comment about improving glib-mkenums usage in future Signed-off-by: Philip Withnall <withnall@endlessm.com> https://github.com/ostreedev/ostree/pull/1329 Closes: #1330 Approved by: cgwalters
2017-11-07 17:53:12 +03:00
# TODO: GLIB_CHECK_VERSION > 2.5x: use --output instead of mv (see https://github.com/ostreedev/ostree/pull/1329)
fetcher: Add "config-flags" construct-only property A lot of effort here just to avoid touching SoupSession directly in ostree_fetcher_new(). The reason will become apparent in subsequent commits. Note this introduces generated enum/flags GTypes using glib-mkenums. I could have just made the property type as plain integer, but doing properties right will henceforth be easier now that the automake-fu is established.
2015-11-10 03:04:42 +03:00
src/libostree/ostree-enumtypes.h: src/libostree/ostree-enumtypes.h.template $(ENUM_TYPES)
$(AM_V_GEN) $(GLIB_MKENUMS) \
build: Fix srcdir != builddir Caught by GContinuous. Also change the file writes to be atomic, otherwise we're not Ctrl-c safe.
2015-12-14 22:19:35 +03:00
--template $< \
$(ENUM_TYPES) > $@.tmp && mv $@.tmp $@
fetcher: Add "config-flags" construct-only property A lot of effort here just to avoid touching SoupSession directly in ostree_fetcher_new(). The reason will become apparent in subsequent commits. Note this introduces generated enum/flags GTypes using glib-mkenums. I could have just made the property type as plain integer, but doing properties right will henceforth be easier now that the automake-fu is established.
2015-11-10 03:04:42 +03:00
build: Ensure enumtypes.h is built before enumtypes.c ostree-enumtypes.c includes ostree-enumtypes.h, so make needs to be told about the dependency. Without it, parallel make could try to build ostree-enumtypes.c before the header file exists. I hit this when running `make -j OSTree-1.0.gir`. Closes: #1322 Approved by: pwithnall
2017-11-03 18:47:16 +03:00
src/libostree/ostree-enumtypes.c: src/libostree/ostree-enumtypes.c.template src/libostree/ostree-enumtypes.h $(ENUM_TYPES)
fetcher: Add "config-flags" construct-only property A lot of effort here just to avoid touching SoupSession directly in ostree_fetcher_new(). The reason will become apparent in subsequent commits. Note this introduces generated enum/flags GTypes using glib-mkenums. I could have just made the property type as plain integer, but doing properties right will henceforth be easier now that the automake-fu is established.
2015-11-10 03:04:42 +03:00
$(AM_V_GEN) $(GLIB_MKENUMS) \
build: Fix srcdir != builddir Caught by GContinuous. Also change the file writes to be atomic, otherwise we're not Ctrl-c safe.
2015-12-14 22:19:35 +03:00
--template $< \
$(ENUM_TYPES) > $@.tmp && mv $@.tmp $@
fetcher: Add "config-flags" construct-only property A lot of effort here just to avoid touching SoupSession directly in ostree_fetcher_new(). The reason will become apparent in subsequent commits. Note this introduces generated enum/flags GTypes using glib-mkenums. I could have just made the property type as plain integer, but doing properties right will henceforth be easier now that the automake-fu is established.
2015-11-10 03:04:42 +03:00
libostree: Don't distribute generated enumtypes in tarballs They are built at "make" time and cleaned up by "make clean", so there is no need to distribute them. Signed-off-by: Simon McVittie <smcv@debian.org> Closes: #665 Approved by: cgwalters
2017-01-27 12:06:39 +03:00
nodist_libostree_1_la_SOURCES = \
fetcher: Add "config-flags" construct-only property A lot of effort here just to avoid touching SoupSession directly in ostree_fetcher_new(). The reason will become apparent in subsequent commits. Note this introduces generated enum/flags GTypes using glib-mkenums. I could have just made the property type as plain integer, but doing properties right will henceforth be easier now that the automake-fu is established.
2015-11-10 03:04:42 +03:00
src/libostree/ostree-enumtypes.h \
src/libostree/ostree-enumtypes.c \
$(NULL)
libostree: Don't distribute generated enumtypes in tarballs They are built at "make" time and cleaned up by "make clean", so there is no need to distribute them. Signed-off-by: Simon McVittie <smcv@debian.org> Closes: #665 Approved by: cgwalters
2017-01-27 12:06:39 +03:00
BUILT_SOURCES += $(nodist_libostree_1_la_SOURCES)
fetcher: Add "config-flags" construct-only property A lot of effort here just to avoid touching SoupSession directly in ostree_fetcher_new(). The reason will become apparent in subsequent commits. Note this introduces generated enum/flags GTypes using glib-mkenums. I could have just made the property type as plain integer, but doing properties right will henceforth be easier now that the automake-fu is established.
2015-11-10 03:04:42 +03:00
CLEANFILES += $(BUILT_SOURCES)
Install a shared library This required a fair bit of surgery because previously ostree.h included otutil.h, but that's supposed to be a private library.
2013-07-27 03:25:07 +04:00
libostree_1_la_SOURCES = \
Add OstreeAsyncProgress, use it for ostree_repo_pull Several APIs in libostree were moved there from the commandline code, and have hardcoded g_print() for progress and notifications. This isn't useful for people who want to write PackageKit backends, custom GUIs and the like. From what I can tell, there isn't really a winning precedent in GLib for progress notifications. PackageKit has the model where the source has GObject properties that change as async ops execute, which isn't bad...but I'd like something a bit more general where say you can have multiple outstanding async ops and sensibly track their state. So, OstreeAsyncProgress is basically a threadsafe property bag with a change notification signal. Use this new API to move the GSConsole usage (i.e. g_print()) out from libostree/ and into ostree/.
2013-10-24 17:10:34 +04:00
src/libostree/ostree-async-progress.c \
Rename ostree-cmdprivate to drop out of introspection I was looking at our `.gir` and noticed we had the cmdprivate bits because the pattern for excluding headers is `-private.h`, which didn't match `cmdprivate.h`.
2022-06-03 00:13:17 +03:00
src/libostree/ostree-cmd-private.h \
src/libostree/ostree-cmd-private.c \
trivial: Add missing files to dist
2013-10-16 00:30:09 +04:00
src/libostree/ostree-core-private.h \
Install a shared library This required a fair bit of surgery because previously ostree.h included otutil.h, but that's supposed to be a private library.
2013-07-27 03:25:07 +04:00
src/libostree/ostree-core.c \
tests: Split RFC 2616 date parsing code out and add tests This makes it testable, and increases its test coverage too 100% of lines, as measured by `make coverage`. Signed-off-by: Philip Withnall <pwithnall@endlessos.org>
2020-10-16 19:05:54 +03:00
src/libostree/ostree-date-utils.c \
src/libostree/ostree-date-utils-private.h \
Make enum generation private by default, export stub symbol When we added enum type generation, the generated symbols used the `ostree_` prefix, and at the time that implied they were public. So we started (if built with libsoup) exporting `ostree_fetcher_config_flags_get_type`. I think it's not worth confusing ABI checkers, so let's export the dummy symbol forever, and switch enums to be private by default. We should revisit this and also export some auto-generated enum types for public enums, but that's a separate patch. Closes: #296 Approved by: gatispaeglis
2016-05-12 17:32:17 +03:00
src/libostree/ostree-dummy-enumtypes.c \
core: Clean up checksumming Don't expose GChecksum in APIs. Add a new stream class which allows us to pass an input stream somewhere, but gather a checksum as it's read. Move some bits of the internals towards binary csums.
2012-04-11 00:40:22 +04:00
src/libostree/ostree-checksum-input-stream.c \
src/libostree/ostree-checksum-input-stream.h \
core: Re-unify on one OSTREE_OBJECT_TYPE_FILE Having the archived vs not distinction in the object system wasn't useful in light of pack files. In fact, we should probably move towards generating a pack file per commit by default.
2012-04-11 23:18:34 +04:00
src/libostree/ostree-chain-input-stream.c \
src/libostree/ostree-chain-input-stream.h \
repo: Add ostree_repo_write_regfile This API is push rather than pull, which makes it much more suitable to use cases like parsing a tar file from external code. Now, we have a large mess in this area internally because the original file writing code was pull based, but static deltas hit the same problem of wanting a push API, so I added this special `OstreeRepoBareContent` just for writing regular files from a push API. Eventually...I'd like to deprecate the pull based API, and rework things so that for regular files the push API is the default, and then `write_content_object()` would be split up into archive/bare cases. In this world the `ostree_repo_write_content()` API would then need to hackily bridge pull to push and it'd be less efficient. Anyways for now due to this bifurcation, this API only works on non-archive repositories, but that's fine for now because that's what I want for the `ostree-ext-container` bits.
2021-04-09 03:35:54 +03:00
src/libostree/ostree-content-writer.c \
src/libostree/ostree-content-writer.h \
deltas: Link to liblzma, add internal API to use it For future static deltas work, we'll be linking to liblzma. Since it's fairly widespread, let's just make it a hard dependency.
2014-04-29 16:56:05 +04:00
src/libostree/ostree-lzma-common.c \
src/libostree/ostree-lzma-common.h \
src/libostree/ostree-lzma-compressor.c \
src/libostree/ostree-lzma-compressor.h \
src/libostree/ostree-lzma-decompressor.c \
src/libostree/ostree-lzma-decompressor.h \
deltas: Implement rollsums This does an rsync-style prepared delta basically. On my test data, it shaves ~6MB of uncompressed data. Not a huge amount, but I expect this to be more useful for things like binaries which embed data, etc.
2015-01-30 18:13:07 +03:00
src/libostree/ostree-rollsum.h \
src/libostree/ostree-rollsum.c \
core: Add code to read/write "varints" Adapted from Google protobufs. For several cases, we want to support e.g. file sizes up to guint64, but paying the cost of 8 bytes for each number is too high. This will be used for static deltas and sizes metadata.
2013-08-15 17:03:21 +04:00
src/libostree/ostree-varint.h \
src/libostree/ostree-varint.c \
deploy: Set the immutable bit on the deployment root This prevents people from creating new directories there and expecting them to be persisted. The OSTree model has all local state to be in /etc and /var. This introduces a compile-time dependency on libe2fsprogs. We're only doing this for the root directory at the moment. https://bugzilla.gnome.org/show_bug.cgi?id=728006
2014-05-30 18:02:01 +04:00
src/libostree/ostree-linuxfsutil.h \
src/libostree/ostree-linuxfsutil.c \
core: Refactor diff to be an internal API For future use by other code.
2012-09-01 01:49:58 +04:00
src/libostree/ostree-diff.c \
core: Add new "mutable tree" class, use it for tar file import The tar import code forced the resuscitation of a hackish "FileTree" data type for representing an in-memory tree. Split this out into an OstreeMutableTree class for future use by any other in-memory tree construction.
2011-12-21 22:34:10 +04:00
src/libostree/ostree-mutable-tree.c \
lib/ref: Add OstreeCollectionRef type for globally unique refs This is a type representing the tuple (collection ID, ref name), which is guaranteed to be globally unique. It will be used in upcoming commits. It introduces the concept of a ‘collection’ which is a unique, curated set of refs which lie in the same trust domain (i.e. all signed by the same key and validated by the same developer). Flathub might be a collection, for example; or the set of OS refs coming from a particular OS vendor. It includes a function for validating collection IDs. Signed-off-by: Philip Withnall <withnall@endlessm.com> Closes: #924 Approved by: cgwalters
2017-06-07 17:27:10 +03:00
src/libostree/ostree-ref.c \
libostree: Make OstreeRemote a public and internal API Previously it was static to ostree-repo.c. Make it usable throughout libostree so it can be used by an upcoming commit, but also expose the typedef and reference counting functions so that opaque OstreeRemote pointers can be used by user code, in anticipation of exposing more of its API publicly in future. Signed-off-by: Philip Withnall <withnall@endlessm.com> Closes: #832 Approved by: cgwalters
2017-04-21 18:25:23 +03:00
src/libostree/ostree-remote.c \
src/libostree/ostree-remote-private.h \
Add an API+CLI to inject metadata for bootable OSTree commits I was doing some rpm-ostree work and I wanted to compare two OSTree commits to see if the kernel has changed. I think this should be a lot more natural. Add `ostree commit --bootable` which calls into a new generic library API `ostree_commit_metadata_for_bootable()` that discovers the kernel version and injects it as an `ostree.linux` metadata key. And for extra clarity, add an `ostree.bootable` key. It's interesting because the "core" OSTree layer is all about generic files, but this is adding special APIs around bootable OSTree commits (as opposed to e.g. flatpak as well as things like rpm-ostree's pkgcache refs). Eventually, I'd like to ensure everyone is using this and hard require this metadata key for the `ostree admin deploy` flow - mainly to prevent accidents.
2021-03-11 04:36:13 +03:00
src/libostree/ostree-repo-os.c \
build: Move sources into src/ again This is necessary if we want to build when srcdir == builddir, otherwise we blow up because "ostree" is a source directory and a binary.
2011-11-15 00:39:38 +04:00
src/libostree/ostree-repo.c \
libostree: Start splitting up the monstrous ostree-repo.c Checkout now lives in its own file.
2013-07-10 03:02:38 +04:00
src/libostree/ostree-repo-checkout.c \
repo: Move commit code to another file ostree-repo.c is a bit too big, and most of the commit code is fairly standalone. https://bugzilla.gnome.org/show_bug.cgi?id=707644
2013-09-05 23:43:07 +04:00
src/libostree/ostree-repo-commit.c \
lib: Add (private) API for checking out commits into a composefs image This supports checking out a commit into a tree which is then converted into a composefs image containing fs-verity digests for all the regular files, and payloads that are relative to a the `repo/objects` directory of a bare ostree repo. Some specal files are always created in the image. This ensures that various directories (usr, etc, boot, var, sysroot) exists in the created image, even if they were not in the source commit. These are needed (as bindmount targets) if you want to boot from the image. In the non-composefs case these are just created as needed in the checked out deploydir, but we can't do that here. This is all controlled by the new ex-integrity config section, which has the following layout: ``` [ex-integrity] fsverity=yes/no/maybe composefs=yes/no/maybe composefs-apply-sig=yes/no composefs-add-metadata=yes/no composefs-keyfiile=/a/path composefs-certfile=/a/path ``` The `fsverity` key overrides the old `ex-fsverity` section if specified. The default for all these is for the new behaviour to be disabled. Additionally, enabling composefs implies fsverity defaults to `maybe`, to avoid having to set both.
2022-06-09 18:15:29 +03:00
src/libostree/ostree-repo-composefs.c \
pull: Move libsoup-related code from ostree-repo.c to ostree-repo-pull.c This centralizes the ifdef's in one file, which will make it easier to write new pull backends. ostree-repo-pull.c is now built unconditionally Closes: #327 Approved by: cgwalters
2016-06-08 21:48:44 +03:00
src/libostree/ostree-repo-pull.c \
lib/pull: Split verify_bindings() out into a cmdprivate method It will be used by the fsck utility in future. We could expose it publicly in future too, if needed. Signed-off-by: Philip Withnall <withnall@endlessm.com> Closes: #1347 Approved by: cgwalters
2017-11-20 15:37:24 +03:00
src/libostree/ostree-repo-pull-private.h \
lib: Move gpg/signapi bits into ostree-repo-pull-verify.c `ostree-repo-pull.c` is huge; separate some of the GPG/signing verification functions into their own file so they're more easily seen.
2020-04-17 04:13:51 +03:00
src/libostree/ostree-repo-pull-verify.c \
libostree: Split off libarchive code
2013-07-10 03:11:37 +04:00
src/libostree/ostree-repo-libarchive.c \
libostree: Move prune into OstreeRepo namespace More library work.
2013-07-10 04:05:31 +04:00
src/libostree/ostree-repo-prune.c \
libostree: Split off -refs.c Continuing to break up ostree-repo.c.
2013-07-10 03:49:00 +04:00
src/libostree/ostree-repo-refs.c \
repo: Move fsverity bits to ostree-repo-verity.c This file will get larger when we start doing more with fsverity.
2021-01-08 00:17:01 +03:00
src/libostree/ostree-repo-verity.c \
libostree: Rename ostree-traverse.h into OstreeRepo namespace This operates on the repo, it might as well be methods on it.
2013-07-10 03:59:39 +04:00
src/libostree/ostree-repo-traverse.c \
libostree: Start splitting up the monstrous ostree-repo.c Checkout now lives in its own file.
2013-07-10 03:02:38 +04:00
src/libostree/ostree-repo-private.h \
build: Move sources into src/ again This is necessary if we want to build when srcdir == builddir, otherwise we blow up because "ostree" is a source directory and a binary.
2011-11-15 00:39:38 +04:00
src/libostree/ostree-repo-file.c \
src/libostree/ostree-repo-file-enumerator.c \
src/libostree/ostree-repo-file-enumerator.h \
libostree: Split off SELinux OstreeSePolicy class It's better if this is independent from the OstreeSysroot; for example, a policy is active in a given deployment root at once, not for a sysroot globally. We can also collect SELinux-related API in one place. Unfortunately at the moment there can be only one instance of this class per process.
2014-02-19 17:40:29 +04:00
src/libostree/ostree-sepolicy.c \
build: Dist ostree-sepolicy-private.h Should fix the Travis builds which actually generate a legacy tarball via Automake. Closes: #755 Approved by: jlebon
2017-03-23 21:29:59 +03:00
src/libostree/ostree-sepolicy-private.h \
libostree: Move a lot more sysroot API here OstreeBootloader is temporarily public API.
2013-09-16 02:07:34 +04:00
src/libostree/ostree-sysroot-private.h \
libostree: Add new OstreeSysroot class At the moment, just a container for a path, but we will start moving admin functionality here.
2013-09-15 22:33:57 +04:00
src/libostree/ostree-sysroot.c \
libostree: Move a lot more sysroot API here OstreeBootloader is temporarily public API.
2013-09-16 02:07:34 +04:00
src/libostree/ostree-sysroot-cleanup.c \
libostree: Nearly complete move of API into OstreeSysroot Move the deployment code too.
2013-09-16 04:16:20 +04:00
src/libostree/ostree-sysroot-deploy.c \
Add an OstreeSysrootUpgrader API This moves some utility code from the ostree tool into the shared library, which will make it easier to consume by external tools.
2014-03-23 16:54:28 +04:00
src/libostree/ostree-sysroot-upgrader.c \
Switch to using a systemd generator for /var If one wants to set up a mount for `/var` in `/etc/fstab`, it won't be mounted since `ostree-prepare-root` set up a bind mount for `/var` to `/sysroot/ostree/$stateroot/var`, and systemd will take the already extant mount over what's in `/etc/fstab`. There are a few options to fix this, but what I settled on is parsing `/etc/fstab` in a generator (exactly like `systemd-fstab-generator` does), except here we look for an explicit mount for `/var`, and if one *isn't* found, synthesize the default ostree mount to the stateroot. Another nice property is that if an admin creates a `var.mount` unit in `/etc` for example, that will also override our mount. Note that today ostree doesn't hard depend on systemd, so this behavior only kicks in if we're built with systemd *and* libmount support (for parsing `/etc/fstab`). I didn't really test that case though. Initially I started writing this as a "pure libc" program, but at one point decided to use `libostree.so` to find the booted deployment. That didn't work out because `/boot` wasn't necessarily mounted and hence we couldn't find the bootloader config. A leftover artifact from this is that the generator code calls into libostree via the "cmd private" infrastructure. But it's an easy way to share code, and doesn't hurt. Closes: #859 Approved by: jlebon
2017-05-11 21:54:12 +03:00
src/libostree/ostree-impl-system-generator.c \
Move Deployment and BootconfigParser into libostree As part of moving admin functionality there. While we are doing this, rename OtConfigParser to OstreeBootConfig parser since it's a better name.
2013-09-15 23:06:31 +04:00
src/libostree/ostree-bootconfig-parser.c \
src/libostree/ostree-deployment.c \
libostree: Make OstreeBootloader private It was only temporarily public while functionality was being merged down; that's done now.
2013-09-16 04:26:13 +04:00
src/libostree/ostree-bootloader.h \
libostree: Move a lot more sysroot API here OstreeBootloader is temporarily public API.
2013-09-16 02:07:34 +04:00
src/libostree/ostree-bootloader.c \
bootloader: Add an aboot (Android) bootloader backend aboot is special in that it packages kernel, initrd, cmdline, dtb and signature one combined image (similar to upcoming unified kernel images). This is then loaded as an image into an aboot partition. This image is signed by the OS vendor and covers everything in the image. So locally on the deployed system it should not be possible to boot an unsigned image (unless signature checking is turned off). We call a shell script aboot-deploy when it is required to write a new image to the aboot partition (a file typically starting with aboot and ending in .img extension). This shell script may also read some configurations from a .cfg file. Signed-off-by: Eric Curtin <ecurtin@redhat.com>
2022-12-13 17:12:25 +03:00
src/libostree/ostree-bootloader-aboot.h \
src/libostree/ostree-bootloader-aboot.c \
libostree: Add initial GRUB2 support In this approach, we drop a /etc/grub.d/15_ostree file which is a hybrid of shell/C that picks up bits from the GRUB2 library (e.g. the block device script generation), and then calls into libostree's GRUB2 code which knows about the BLS entries. This is admittedly ugly. There exists another approach for GRUB2 to learn the BLS specification. However, the spec has a few issues: https://www.redhat.com/archives/anaconda-devel-list/2014-July/msg00002.html This approach also gives a bit more control to the admin via the naming of the 15_ostree symlink; they can easily disable it: Or reorder the ostree entries ahead of 10_linux: Also, this approach doesn't require patches for grub2, which is an issue with the pressure to backport (rpm-)OSTree to EL7.
2014-10-11 16:59:06 +04:00
src/libostree/ostree-bootloader-grub2.h \
src/libostree/ostree-bootloader-grub2.c \
bootloader: Add a zipl bootloader backend zipl is a bit special in that it parses the BLS config files directly *but* we need to run the command to update the "boot block". Hence, we're not generating a separate config file like the other backends. Instead, extend the bootloader interface with a `post_bls_sync` method that is run in the same place we swap the `boot/loader` symlink. We write a "stamp file" in `/boot` that says we need to run this command. The reason we use stamp file is to prevent the case where the system is interrupted after BLS file is updated, but before zipl is triggered, then zipl boot records are not updated. This opens the door to making things eventually-consistent/reconcilable by later adding a systemd unit to run `zipl` if we're interrupted via a systemd unit - I think we should eventually take this approach everywhere rather than requiring `/boot/loader` to be a symlink. Author: Colin Walters <walters@verbum.org> Tested-by: Tuan Hoang <tmhoang@linux.ibm.com> Co-Authored-By: Tuan Hoang <tmhoang@linux.ibm.com>
2019-10-14 22:22:19 +03:00
src/libostree/ostree-bootloader-zipl.h \
src/libostree/ostree-bootloader-zipl.c \
libostree: Move a lot more sysroot API here OstreeBootloader is temporarily public API.
2013-09-16 02:07:34 +04:00
src/libostree/ostree-bootloader-syslinux.h \
src/libostree/ostree-bootloader-syslinux.c \
src/libostree/ostree-bootloader-uboot.h \
src/libostree/ostree-bootloader-uboot.c \
Initial basic static delta code drop This has a very basic level of functionality (deltas can be generated, and applied offline). There is only some stubbed out pull code to fetch them via HTTP. But, better to commit this now and improve it from a known starting point, rather than have it languish in a branch.
2013-08-15 17:17:37 +04:00
src/libostree/ostree-repo-static-delta-core.c \
src/libostree/ostree-repo-static-delta-processing.c \
src/libostree/ostree-repo-static-delta-compilation.c \
deltas: Search for similar objects (possibly renamed across directories) The previous diff algorithm was file tree based, and only looked at modified files that lived at the same path. However, components like the Linux kernel have versioned subdirectories, e.g. /usr/lib/modules/$kver/.../ext4.ko. We want to be able to detect these "modified renames" so that we can compute diffs (rollsum, bsdiff).
2015-02-11 11:29:14 +03:00
src/libostree/ostree-repo-static-delta-compilation-analysis.c \
Initial basic static delta code drop This has a very basic level of functionality (deltas can be generated, and applied offline). There is only some stubbed out pull code to fetch them via HTTP. But, better to commit this now and improve it from a known starting point, rather than have it languish in a branch.
2013-08-15 17:17:37 +04:00
src/libostree/ostree-repo-static-delta-private.h \
libostree: Add g_autoptr() support for the public types To avoid breaking the ostree users we hide the autoptr setup behind an OSTREE_WITH_AUTOCLEANUPS variable. The variable is set to 0 by default, so users that want to start using them, have to define the variable themselves to 1. Probably after some transition period, the variable will be set 1 by default. This is conditional on GLib >= 2.44.0 being available. It does not bump ostree's dependency on GLib. Closes: #295 Approved by: cgwalters
2016-05-12 15:42:26 +03:00
src/libostree/ostree-autocleanups.h \
Make P2P API public (no longer experimental) Currently the API that allows P2P operations (e.g. pulling an ostree ref from a LAN or USB source) is hidden behind the configure flag --enable-experimental-api. This commit makes the API public and makes that flag essentially a no-op (leaving it in place in case we want to use it again in the future). The P2P API has been tested over the last several months and proven to work. This means that since we're no longer using the "experimental" feature flag, P2P builds of Flatpak will fail when using versions of OSTree from this commit onwards, until Flatpak is patched in the near future. If you want to build Flatpak < 0.11.8 with P2P enabled and link against OSTree 2018.6, you'll have to patch Flatpak. However, since Flatpak won't yet have a hard dependency on OSTree 2018.6, it needs a new way to determine if the P2P API in OSTree is available, so this commit adds a "p2p" feature flag. This way the feature set is more semantically correct than if we had continued to use the "experimental" feature flag. In addition to making the P2P API public, this commit makes the P2P unit tests run by default, removes the f27-experimental CI instance that's no longer needed, changes a few man pages to reflect the changes, and updates the bash completion script to accept the new commands and options. Closes: #1596 Approved by: cgwalters
2018-05-23 01:55:14 +03:00
src/libostree/ostree-bloom.c \
src/libostree/ostree-bloom-private.h \
src/libostree/ostree-repo-finder.c \
src/libostree/ostree-repo-finder-avahi.c \
src/libostree/ostree-repo-finder-config.c \
src/libostree/ostree-repo-finder-mount.c \
src/libostree/ostree-repo-finder-override.c \
lib/kargs: Make API public and upstream new rpm-ostree APIs This change makes public the current kargs API in src/libostree/ostree-kernel-args.c and adds documentations. Upstreams the new kargs API from rpm-ostree/src/libpriv/rpmostree-kargs-process.c Merges libostree_kernel_args_la_SOURCES to libostree_1_la_SOURCES in Makefile-libostree.am Upstreams tests/check/test-kargs.c from rpm-ostree. Closes: #1833 Closes: #1869 Approved by: jlebon
2019-05-28 21:02:54 +03:00
src/libostree/ostree-kernel-args.h \
kernel-args: Move private functions out of public header External users can't call `_` prefixed APIs, so move them to a `-private.h`.
2023-07-23 17:26:30 +03:00
src/libostree/ostree-kernel-args-private.h \
lib/kargs: Make API public and upstream new rpm-ostree APIs This change makes public the current kargs API in src/libostree/ostree-kernel-args.c and adds documentations. Upstreams the new kargs API from rpm-ostree/src/libpriv/rpmostree-kargs-process.c Merges libostree_kernel_args_la_SOURCES to libostree_1_la_SOURCES in Makefile-libostree.am Upstreams tests/check/test-kargs.c from rpm-ostree. Closes: #1833 Closes: #1869 Approved by: jlebon
2019-05-28 21:02:54 +03:00
src/libostree/ostree-kernel-args.c \
De-recursify source tree
2011-11-02 23:45:32 +04:00
$(NULL)
core: Support for committing from any libarchive-supported format We really want the ability to take a .tar.gz and directly import it into a repository, without creating a temporary filesystem tree. First, doing it this way is significantly faster. Also, this allows us to handle importing tar files with e.g. uid 0 files into packed repositories as non-root, which is very useful for tests and builds.
2011-12-04 21:14:08 +04:00
if USE_LIBARCHIVE
Install a shared library This required a fair bit of surgery because previously ostree.h included otutil.h, but that's supposed to be a private library.
2013-07-27 03:25:07 +04:00
libostree_1_la_SOURCES += src/libostree/ostree-libarchive-input-stream.h \
core: Support for committing from any libarchive-supported format We really want the ability to take a .tar.gz and directly import it into a repository, without creating a temporary filesystem tree. First, doing it this way is significantly faster. Also, this allows us to handle importing tar files with e.g. uid 0 files into packed repositories as non-root, which is very useful for tests and builds.
2011-12-04 21:14:08 +04:00
src/libostree/ostree-libarchive-input-stream.c \
Define and use cleanup helpers for libarchive This should fix some of the ASAN leaks around libarchive usage, and is generally better. Closes: #609 Approved by: jlebon
2016-12-02 21:34:32 +03:00
src/libostree/ostree-libarchive-private.h \
core: Support for committing from any libarchive-supported format We really want the ability to take a .tar.gz and directly import it into a repository, without creating a temporary filesystem tree. First, doing it this way is significantly faster. Also, this allows us to handle importing tar files with e.g. uid 0 files into packed repositories as non-root, which is very useful for tests and builds.
2011-12-04 21:14:08 +04:00
$(NULL)
endif
pull: Add tls-client-cert-{path,key} (if we have new enough libsoup) This is an actually working version of client-side certificates. Depends on: See: https://bugzilla.gnome.org/show_bug.cgi?id=334021 We detect whether libsoup is new enough for this. https://bugzilla.gnome.org/show_bug.cgi?id=729356
2014-05-01 20:55:13 +04:00
if HAVE_LIBSOUP_CLIENT_CERTS
libostree_1_la_SOURCES += \
src/libostree/ostree-tls-cert-interaction.c \
Remove OstreeTlsCertInteraction bits from introspection We filter out everything named `-private.h` from scanning, which differs from the gtk-doc exclude. Eventually this will be solved when we switch to the new gir-based docs. Came up in https://github.com/ostreedev/ostree-rs/pull/34#discussion_r723337772
2021-10-06 19:42:56 +03:00
src/libostree/ostree-tls-cert-interaction-private.h \
pull: Add tls-client-cert-{path,key} (if we have new enough libsoup) This is an actually working version of client-side certificates. Depends on: See: https://bugzilla.gnome.org/show_bug.cgi?id=334021 We detect whether libsoup is new enough for this. https://bugzilla.gnome.org/show_bug.cgi?id=729356
2014-05-01 20:55:13 +04:00
$(NULL)
endif
lib/repo-finder: Add Avahi based OstreeRepoFinder implementation This is a more complex implementation of OstreeRepoFinder which resolves ref names to remote URIs by looking for refs advertised by peers on the local network using DNS-SD records and mDNS (Avahi). The idea is to allow OS and app updates to be propagated over local networks, without the internet. It requires an OSTree server and code to generate the DNS-SD adverts in order to be fully functional — support for this will be added separately. Unit tests are included. Includes fixes by Krzesimir Nowak <krzesimir@kinvolk.io>. Signed-off-by: Philip Withnall <withnall@endlessm.com> Closes: #924 Approved by: cgwalters
2017-04-19 02:13:28 +03:00
if USE_AVAHI
libostree_1_la_SOURCES += \
src/libostree/ostree-repo-finder-avahi-parser.c \
src/libostree/ostree-repo-finder-avahi-private.h \
$(NULL)
endif # USE_AVAHI
core: Support for committing from any libarchive-supported format We really want the ability to take a .tar.gz and directly import it into a repository, without creating a temporary filesystem tree. First, doing it this way is significantly faster. Also, this allows us to handle importing tar files with e.g. uid 0 files into packed repositories as non-root, which is very useful for tests and builds.
2011-12-04 21:14:08 +04:00
build: Conditionally build GPGME-related sources Do not build GPGME-related sources if flag USE_GPGME is not defined. Signed-off-by: Denis Pynkin <denis.pynkin@collabora.com> Closes: #1889 Approved by: cgwalters
2019-05-19 16:47:45 +03:00
if USE_GPGME
libostree_1_la_SOURCES += \
src/libostree/ostree-gpg-verifier.c \
src/libostree/ostree-gpg-verifier.h \
src/libostree/ostree-gpg-verify-result.c \
src/libostree/ostree-gpg-verify-result-private.h \
$(NULL)
gpg: add dummy public interface Add dummy stubs for GPG public functions to be compiled instead of original code in case if support of GPG is disabled. Need that to keep API backward compatibility. Based on original code from file `ostree-gpg-verify-result.c`. Signed-off-by: Denis Pynkin <denis.pynkin@collabora.com> Closes: #1889 Approved by: cgwalters
2019-07-21 23:40:32 +03:00
else
libostree_1_la_SOURCES += \
src/libostree/ostree-gpg-verify-result-dummy.c \
$(NULL)
build: Conditionally build GPGME-related sources Do not build GPGME-related sources if flag USE_GPGME is not defined. Signed-off-by: Denis Pynkin <denis.pynkin@collabora.com> Closes: #1889 Approved by: cgwalters
2019-05-19 16:47:45 +03:00
endif # USE_GPGME
build-sys: Add "release build" flag, use for symbol versioning I was trying to do a release and move the symbols from `-devel.sym` into `-release.sym`, but it turns out that at least GNU binutils `ld` treats an empty version script as a syntax error. Fix this by adding a "release build" flag, and only include `-devel` in non-release builds. This would also make it easier to inject that flag into our `.pc` and `ostree-version.h` and `ostree --version` metadata, but I didn't do that yet. EDIT: Turns out a simpler fix is just to add an empty section. However I kept this commit since it's a useful sanity check for whether we should include `-devel.sym` in builds, and we may want to inject the metadata later. Closes: #942 Approved by: jlebon
2017-06-19 17:23:21 +03:00
symbol_files = $(top_srcdir)/src/libostree/libostree-released.sym
Release 2020.8
2020-11-17 13:14:16 +03:00
Add an API+CLI to inject metadata for bootable OSTree commits I was doing some rpm-ostree work and I wanted to compare two OSTree commits to see if the kernel has changed. I think this should be a lot more natural. Add `ostree commit --bootable` which calls into a new generic library API `ostree_commit_metadata_for_bootable()` that discovers the kernel version and injects it as an `ostree.linux` metadata key. And for extra clarity, add an `ostree.bootable` key. It's interesting because the "core" OSTree layer is all about generic files, but this is adding special APIs around bootable OSTree commits (as opposed to e.g. flatpak as well as things like rpm-ostree's pkgcache refs). Eventually, I'd like to ensure everyone is using this and hard require this metadata key for the `ostree admin deploy` flow - mainly to prevent accidents.
2021-03-11 04:36:13 +03:00
# Uncomment this include when adding new development symbols.
Add `ostree admin post-copy` command This command will apply fs-verity on all objects that need it and needs to be called when an ostree deployment has been copied on a file-by-file basis, which would loose information such as fs-verity. This is needed by osbuild which works by creating the final image in a rootfs, and then separately copying that rootfs file-by-file to a loopback mounted filesystem image.
2023-11-13 19:33:57 +03:00
if BUILDOPT_IS_DEVEL_BUILD
configure: post-release version bump
2023-12-05 02:29:13 +03:00
#symbol_files += $(top_srcdir)/src/libostree/libostree-devel.sym
Add `ostree admin post-copy` command This command will apply fs-verity on all objects that need it and needs to be called when an ostree deployment has been copied on a file-by-file basis, which would loose information such as fs-verity. This is needed by osbuild which works by creating the final image in a rootfs, and then separately copying that rootfs file-by-file to a loopback mounted filesystem image.
2023-11-13 19:33:57 +03:00
endif
Release 2020.8
2020-11-17 13:14:16 +03:00
lib: Split symbol versioning into -released and -devel So far a lot of submitted PR have added symbols into the first section. Split the file into `-released` and `-devel` to make this more obvious. To further enforce things, we hardcode a checksum of the `-released` file in `test-symbols.sh`. Only release commits should update that checksum. Did you notice I like checksums? Closes: #931 Approved by: pwithnall
2017-06-15 04:44:04 +03:00
# http://blog.jgc.org/2007/06/escaping-comma-and-space-in-gnu-make.html
wl_versionscript_arg = -Wl,--version-script=
build: Ensure all .sym files are distributed in tarballs Since we’re using a custom variable for listing the .sym files, automake’s magic support for automatically distributing all files in conditionals doesn’t work, and the devel and experimental .sym files were only being distributed if `make dist` was run on a source tree which had been configured with --enable-experimental-api or not a release flag. Fix that by explicitly listing all the .sym files in EXTRA_DIST. Specifically, this fixes the case of trying to compile with --enable-experimental-api from a release tarball which was disted with --disable-experimental-api. Signed-off-by: Philip Withnall <withnall@endlessm.com> Closes: #1001 Approved by: cgwalters
2017-07-12 15:58:16 +03:00
EXTRA_DIST += \
$(top_srcdir)/src/libostree/libostree-devel.sym \
$(top_srcdir)/src/libostree/libostree-released.sym \
$(NULL)
lib: Split symbol versioning into -released and -devel So far a lot of submitted PR have added symbols into the first section. Split the file into `-released` and `-devel` to make this more obvious. To further enforce things, we hardcode a checksum of the `-released` file in `test-symbols.sh`. Only release commits should update that checksum. Did you notice I like checksums? Closes: #931 Approved by: pwithnall
2017-06-15 04:44:04 +03:00
Factor out a libotcore This will contain logic shared between ostree-prepare-root and libostree-1.so. It will just link to libgio.so, so as to avoid pulling in e.g. libcurl and other things. In other words, `ostree-prepare-root` will not link to `libostree-1.so`, but will pull in just what it needs from this library.
2023-07-07 23:31:58 +03:00
libostree_1_la_CFLAGS = $(AM_CFLAGS) -I$(srcdir)/bsdiff -I$(srcdir)/libglnx -I$(srcdir)/composefs -I$(srcdir)/src/libotutil -I$(srcdir)/src/libotcore -I$(srcdir)/src/libostree -I$(builddir)/src/libostree \
src/generator: Move all logic into libostree-1.so This pushes down the code for parsing the `ostree=` cmdline in the generator into code that's part of libostree-1.so. This is prep for using logic shared in libotcore.la. But in general it's just cleaner to also keep the binary entrypoint to just be a trampoline into the C library.
2023-07-23 17:47:19 +03:00
-I$(srcdir)/src/switchroot \
Add --with-crypto=gnutls Introduce support for GnuTLS for computing cryptograpic hashes, similar to the OpenSSL backend. A reason to do this is some distributors want to avoid GPLv3, and GPG pulls that in. A possible extension of using GnuTLS would be replacing the GPG signing with `PKCS#7` signatures and `X.509` keys. We also support `--with-crypto=openssl`, which has the same effect as `--with-openssl`, and continues to be supported. Changes by Colin Walters <walters@verbum.org>: - Drop libgcrypt option for now - Unify buildsystem on --with-crypto Link: https://mail.gnome.org/archives/ostree-list/2017-June/msg00002.html Signed-off-by: Jussi Laako <jussi.laako@linux.intel.com> Closes: #1189 Approved by: cgwalters
2017-06-13 16:56:21 +03:00
$(OT_INTERNAL_GIO_UNIX_CFLAGS) $(OT_INTERNAL_GPGME_CFLAGS) $(OT_DEP_LZMA_CFLAGS) $(OT_DEP_ZLIB_CFLAGS) $(OT_DEP_CRYPTO_CFLAGS) \
s390x: add LUKS keyfile to 'sd-boot' This allows to use Secure Execution with LUKS encrypted boot disk, key and cryptab are stored only in 'sd-boot' encrypted image. Signed-off-by: Nikita Dubrovskii <nikita@linux.ibm.com>
2022-01-17 17:59:54 +03:00
-fvisibility=hidden '-D_OSTREE_PUBLIC=__attribute__((visibility("default"))) extern' \
-DPKGLIBEXECDIR=\"$(pkglibexecdir)\"
lib: Split symbol versioning into -released and -devel So far a lot of submitted PR have added symbols into the first section. Split the file into `-released` and `-devel` to make this more obvious. To further enforce things, we hardcode a checksum of the `-released` file in `test-symbols.sh`. Only release commits should update that checksum. Did you notice I like checksums? Closes: #931 Approved by: pwithnall
2017-06-15 04:44:04 +03:00
libostree_1_la_LDFLAGS = -version-number 1:0:0 -Bsymbolic-functions $(addprefix $(wl_versionscript_arg),$(symbol_files))
Factor out a libotcore This will contain logic shared between ostree-prepare-root and libostree-1.so. It will just link to libgio.so, so as to avoid pulling in e.g. libcurl and other things. In other words, `ostree-prepare-root` will not link to `libostree-1.so`, but will pull in just what it needs from this library.
2023-07-07 23:31:58 +03:00
libostree_1_la_LIBADD = libotutil.la libotcore.la libglnx.la libbsdiff.la $(OT_INTERNAL_GIO_UNIX_LIBS) $(OT_INTERNAL_GPGME_LIBS) \
Add --with-crypto=gnutls Introduce support for GnuTLS for computing cryptograpic hashes, similar to the OpenSSL backend. A reason to do this is some distributors want to avoid GPLv3, and GPG pulls that in. A possible extension of using GnuTLS would be replacing the GPG signing with `PKCS#7` signatures and `X.509` keys. We also support `--with-crypto=openssl`, which has the same effect as `--with-openssl`, and continues to be supported. Changes by Colin Walters <walters@verbum.org>: - Drop libgcrypt option for now - Unify buildsystem on --with-crypto Link: https://mail.gnome.org/archives/ostree-list/2017-June/msg00002.html Signed-off-by: Jussi Laako <jussi.laako@linux.intel.com> Closes: #1189 Approved by: cgwalters
2017-06-13 16:56:21 +03:00
$(OT_DEP_LZMA_LIBS) $(OT_DEP_ZLIB_LIBS) $(OT_DEP_CRYPTO_LIBS)
build-sys: Link with -ldl for rust build I didn't dive into this too much, it looks like something in rust changed that broke our build. Probably libstd gained a dependency on `-ldl` or so, and that's handled by cargo? Anyways linking against it isn't going to hurt. Closes: #1391 Approved by: smcv
2018-01-02 17:54:52 +03:00
# Some change between rust-1.21.0-1.fc27 and rust-1.22.1-1.fc27.x86_64
oxidation: Add implementation of bupsplit in Rust This is an initial drop of "oxidation", or adding implementation of components in Rust. The bupsplit code is a good target - no dependencies, just computation. Translation into Rust had a few twists - - The C code relies a lot on overflowing unsigned ints, and also on the C promotion rules for e.g. `uint8_t -> int32_t` - There were some odd loops that I introduced bugs in while translating...in particular, the function always returns `len`, but I mistakenly translated to `len+1`, resulting in an OOB read on the C side, which was hard to debug. On the plus side, an off-by-one array indexing in the Rust code paniced nicely. In practice, we'll need a lot more build infrastructure to make this work, such as using `cargo vendor` when producing build artifacts for example. Also, Cargo is yet another thing we need to cache. Where do we go with this? Well, I think we should merge this, it's not a lot of code. We can just have it be an alternative CI target. Should we do a lot more right now? Probably not immediately, but I find the medium/long term prospects pretty exciting! Closes: #656 Approved by: jlebon
2017-01-25 05:43:53 +03:00
libostree_1_la_LIBADD += $(bupsplitpath)
lib: Split symbol versioning into -released and -devel So far a lot of submitted PR have added symbols into the first section. Split the file into `-released` and `-devel` to make this more obvious. To further enforce things, we hardcode a checksum of the `-released` file in `test-symbols.sh`. Only release commits should update that checksum. Did you notice I like checksums? Closes: #931 Approved by: pwithnall
2017-06-15 04:44:04 +03:00
EXTRA_libostree_1_la_DEPENDENCIES = $(symbol_files)
build: distribute libostree.sym in tarballs Signed-off-by: Simon McVittie <smcv@debian.org> Closes: #337 Approved by: cgwalters
2016-06-12 12:36:44 +03:00
core: Support for committing from any libarchive-supported format We really want the ability to take a .tar.gz and directly import it into a repository, without creating a temporary filesystem tree. First, doing it this way is significantly faster. Also, this allows us to handle importing tar files with e.g. uid 0 files into packed repositories as non-root, which is very useful for tests and builds.
2011-12-04 21:14:08 +04:00
if USE_LIBARCHIVE
Install a shared library This required a fair bit of surgery because previously ostree.h included otutil.h, but that's supposed to be a private library.
2013-07-27 03:25:07 +04:00
libostree_1_la_CFLAGS += $(OT_DEP_LIBARCHIVE_CFLAGS)
libostree_1_la_LIBADD += $(OT_DEP_LIBARCHIVE_LIBS)
core: Support for committing from any libarchive-supported format We really want the ability to take a .tar.gz and directly import it into a repository, without creating a temporary filesystem tree. First, doing it this way is significantly faster. Also, this allows us to handle importing tar files with e.g. uid 0 files into packed repositories as non-root, which is very useful for tests and builds.
2011-12-04 21:14:08 +04:00
endif
core: Install unversioned .so, and kill .la file This avoids Yocto barfing on a versioned shared library symbolic link without a -dev package.
2011-12-19 03:37:48 +04:00
lib/repo-finder: Add Avahi based OstreeRepoFinder implementation This is a more complex implementation of OstreeRepoFinder which resolves ref names to remote URIs by looking for refs advertised by peers on the local network using DNS-SD records and mDNS (Avahi). The idea is to allow OS and app updates to be propagated over local networks, without the internet. It requires an OSTree server and code to generate the DNS-SD adverts in order to be fully functional — support for this will be added separately. Unit tests are included. Includes fixes by Krzesimir Nowak <krzesimir@kinvolk.io>. Signed-off-by: Philip Withnall <withnall@endlessm.com> Closes: #924 Approved by: cgwalters
2017-04-19 02:13:28 +03:00
if USE_AVAHI
libostree_1_la_CFLAGS += $(OT_DEP_AVAHI_CFLAGS)
libostree_1_la_LIBADD += $(OT_DEP_AVAHI_LIBS)
endif
build: fix systemd feature advertisement 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
2020-01-21 15:37:52 +03:00
if BUILDOPT_SYSTEMD
lib: Use sd_journal directly (optionally) This was the last caller of libgsystem that isn't `gs_file_get_path_cached()`. I think the use case ostree has where the same code can be called via command line and via a shared library *and* via a daemon is rather unusual, so let's just copy the code for logging from libgsystem into here. For example rpm-ostree hard depends on a daemon mode, so it'll just use `sd_journal` directly. Closes: #341 Approved by: jlebon
2016-06-14 20:12:21 +03:00
libostree_1_la_CFLAGS += $(LIBSYSTEMD_CFLAGS)
libostree_1_la_LIBADD += $(LIBSYSTEMD_LIBS)
endif
libcurl backend For rpm-ostree, we already link to libcurl indirectly via librepo, and only having one HTTP library in process makes sense. Further, libcurl is (I think) more popular in the embedded space. It also supports HTTP/2.0 today, which is a *very* nice to have for OSTree. This seems to be working fairly well for me in my local testing, but it's obviously brand new nontrivial code, so it's going to need some soak time. The ugliest part of this is having to vendor in the soup-url code. With Oxidation we could follow the path of Firefox and use the [Servo URL parser](https://github.com/servo/rust-url). Having to redo cookie parsing also sucked, and that would also be a good oxidation target. But that's for the future. Closes: #641 Approved by: jlebon
2016-12-08 05:02:30 +03:00
if USE_CURL_OR_SOUP
Install a shared library This required a fair bit of surgery because previously ostree.h included otutil.h, but that's supposed to be a private library.
2013-07-27 03:25:07 +04:00
libostree_1_la_SOURCES += \
libostree: Move pull code into here More library work.
2013-07-10 04:14:53 +04:00
src/libostree/ostree-fetcher.h \
fetcher: Move high level functions into "fetcher-util" Conceptually these now lay on top of the core API, and don't reference libsoup. This is preparation for libcurl porting, but it's also just generally better. Closes: #636 Approved by: jlebon
2016-12-23 04:34:07 +03:00
src/libostree/ostree-fetcher-util.h \
src/libostree/ostree-fetcher-util.c \
libcurl backend For rpm-ostree, we already link to libcurl indirectly via librepo, and only having one HTTP library in process makes sense. Further, libcurl is (I think) more popular in the embedded space. It also supports HTTP/2.0 today, which is a *very* nice to have for OSTree. This seems to be working fairly well for me in my local testing, but it's obviously brand new nontrivial code, so it's going to need some soak time. The ugliest part of this is having to vendor in the soup-url code. With Oxidation we could follow the path of Firefox and use the [Servo URL parser](https://github.com/servo/rust-url). Having to redo cookie parsing also sucked, and that would also be a good oxidation target. But that's for the future. Closes: #641 Approved by: jlebon
2016-12-08 05:02:30 +03:00
src/libostree/ostree-fetcher-uri.c \
Add repository "summary" file and metalink support For Fedora and potentially other distributions which use globally distributed mirrors, metalink is a popular solution to redirect clients to a dynamic set of mirrors. In order to make metalink work though, it needs *one* file which can be checksummed. (Well, potentially we could explode all refs into the metalink.xml, but that would be a lot more invasive, and a bit weird as we'd end up checksumming the checksum file). This commit adds a new command: $ ostree summary -u To regenerate the summary file. Can only be run by one process at a time. After that's done, the metalink can be generated based on it, and the client fetch code will parse and load it. https://bugzilla.gnome.org/show_bug.cgi?id=729585
2014-08-01 02:50:19 +04:00
src/libostree/ostree-metalink.h \
src/libostree/ostree-metalink.c \
libostree: Move pull code into here More library work.
2013-07-10 04:14:53 +04:00
$(NULL)
libcurl backend For rpm-ostree, we already link to libcurl indirectly via librepo, and only having one HTTP library in process makes sense. Further, libcurl is (I think) more popular in the embedded space. It also supports HTTP/2.0 today, which is a *very* nice to have for OSTree. This seems to be working fairly well for me in my local testing, but it's obviously brand new nontrivial code, so it's going to need some soak time. The ugliest part of this is having to vendor in the soup-url code. With Oxidation we could follow the path of Firefox and use the [Servo URL parser](https://github.com/servo/rust-url). Having to redo cookie parsing also sucked, and that would also be a good oxidation target. But that's for the future. Closes: #641 Approved by: jlebon
2016-12-08 05:02:30 +03:00
endif
fetcher: add libsoup3 backend The default is still soup2, you can use --with-soup3 to enable the soup3 backend instead.
2022-02-17 22:12:18 +03:00
# Only enable one fetcher backend.
libcurl backend For rpm-ostree, we already link to libcurl indirectly via librepo, and only having one HTTP library in process makes sense. Further, libcurl is (I think) more popular in the embedded space. It also supports HTTP/2.0 today, which is a *very* nice to have for OSTree. This seems to be working fairly well for me in my local testing, but it's obviously brand new nontrivial code, so it's going to need some soak time. The ugliest part of this is having to vendor in the soup-url code. With Oxidation we could follow the path of Firefox and use the [Servo URL parser](https://github.com/servo/rust-url). Having to redo cookie parsing also sucked, and that would also be a good oxidation target. But that's for the future. Closes: #641 Approved by: jlebon
2016-12-08 05:02:30 +03:00
if USE_CURL
libostree_1_la_SOURCES += src/libostree/ostree-fetcher-curl.c \
$(NULL)
libostree_1_la_CFLAGS += $(OT_DEP_CURL_CFLAGS)
libostree_1_la_LIBADD += $(OT_DEP_CURL_LIBS)
else
fetcher: add libsoup3 backend The default is still soup2, you can use --with-soup3 to enable the soup3 backend instead.
2022-02-17 22:12:18 +03:00
if USE_LIBSOUP3
libostree_1_la_SOURCES += src/libostree/ostree-fetcher-soup3.c
libostree_1_la_CFLAGS += $(OT_INTERNAL_SOUP_CFLAGS)
libostree_1_la_LIBADD += $(OT_INTERNAL_SOUP_LIBS)
else
libcurl backend For rpm-ostree, we already link to libcurl indirectly via librepo, and only having one HTTP library in process makes sense. Further, libcurl is (I think) more popular in the embedded space. It also supports HTTP/2.0 today, which is a *very* nice to have for OSTree. This seems to be working fairly well for me in my local testing, but it's obviously brand new nontrivial code, so it's going to need some soak time. The ugliest part of this is having to vendor in the soup-url code. With Oxidation we could follow the path of Firefox and use the [Servo URL parser](https://github.com/servo/rust-url). Having to redo cookie parsing also sucked, and that would also be a good oxidation target. But that's for the future. Closes: #641 Approved by: jlebon
2016-12-08 05:02:30 +03:00
if USE_LIBSOUP
libostree_1_la_SOURCES += src/libostree/ostree-fetcher-soup.c
Install a shared library This required a fair bit of surgery because previously ostree.h included otutil.h, but that's supposed to be a private library.
2013-07-27 03:25:07 +04:00
libostree_1_la_CFLAGS += $(OT_INTERNAL_SOUP_CFLAGS)
libostree_1_la_LIBADD += $(OT_INTERNAL_SOUP_LIBS)
endif
libcurl backend For rpm-ostree, we already link to libcurl indirectly via librepo, and only having one HTTP library in process makes sense. Further, libcurl is (I think) more popular in the embedded space. It also supports HTTP/2.0 today, which is a *very* nice to have for OSTree. This seems to be working fairly well for me in my local testing, but it's obviously brand new nontrivial code, so it's going to need some soak time. The ugliest part of this is having to vendor in the soup-url code. With Oxidation we could follow the path of Firefox and use the [Servo URL parser](https://github.com/servo/rust-url). Having to redo cookie parsing also sucked, and that would also be a good oxidation target. But that's for the future. Closes: #641 Approved by: jlebon
2016-12-08 05:02:30 +03:00
endif
fetcher: add libsoup3 backend The default is still soup2, you can use --with-soup3 to enable the soup3 backend instead.
2022-02-17 22:12:18 +03:00
endif
Install a shared library This required a fair bit of surgery because previously ostree.h included otutil.h, but that's supposed to be a private library.
2013-07-27 03:25:07 +04:00
deploy: Handle a read-only /boot I'd like to encourage people to make OSTree-managed systems more strictly read-only in multiple places. Ideally everywhere is read-only normally besides `/var/`, `/tmp/`, and `/run`. `/boot` is a good example of something to make readonly. Particularly now that there's work on the `admin unlock` verb, we need to protect the system better against things like `rpm -Uvh kernel.rpm` because the RPM-packaged kernel won't understand how to do OSTree right. In order to make this work of course, we *do* need to remount `/boot` as writable when we're doing an upgrade that changes the kernel configuration. So the strategy is to detect whether it's read-only, and if so, temporarily mount read-write, then remount read-only when the upgrade is done. We can generalize this in the future to also do `/etc` (and possibly `/sysroot/ostree/` although that gets tricky). One detail: In order to detect "is this path a mountpoint" is nontrivial - I looked at copying the systemd code, but the right place is to use `libmount` anyways.
2016-03-21 17:37:38 +03:00
if USE_LIBMOUNT
libostree_1_la_CFLAGS += $(OT_DEP_LIBMOUNT_CFLAGS)
libostree_1_la_LIBADD += $(OT_DEP_LIBMOUNT_LIBS)
endif
build: Include SELinux cflags with libostree build too This is likely another issue with newer automake. https://bugzilla.gnome.org/738875
2014-10-20 19:06:51 +04:00
if USE_SELINUX
libostree_1_la_CFLAGS += $(OT_DEP_SELINUX_CFLAGS)
libostree_1_la_LIBADD += $(OT_DEP_SELINUX_LIBS)
endif
lib/sign: initial implementation Added the initial version of signing interface allowing to allowing to sign and verify commits. Implemented initial signing modules: - dummy -- simple module allowing to sign/verify with ASCII string - ed25519 -- module allowing to sign/verify commit with ed25519 (EdDSA) signature scheme provided by libsodium library. Signed-off-by: Denis Pynkin <denis.pynkin@collabora.com>
2019-07-29 02:32:28 +03:00
libostree_1_la_SOURCES += \
src/libostree/ostree-sign.c \
src/libostree/ostree-sign.h \
src/libostree/ostree-sign-dummy.c \
src/libostree/ostree-sign-dummy.h \
src/libostree/ostree-sign-ed25519.c \
src/libostree/ostree-sign-ed25519.h \
lib: Provide internal summary signing with separate directory Refactor the summary signing APIs to use internal versions where the directory fd containing the summary can be found. The existing signing APIs still uses the repo directory fd, but this will allow using a temporary directory for the summary and signature in the new metadata generating API.
2020-01-21 21:56:09 +03:00
src/libostree/ostree-sign-private.h \
lib/sign: initial implementation Added the initial version of signing interface allowing to allowing to sign and verify commits. Implemented initial signing modules: - dummy -- simple module allowing to sign/verify with ASCII string - ed25519 -- module allowing to sign/verify commit with ed25519 (EdDSA) signature scheme provided by libsodium library. Signed-off-by: Denis Pynkin <denis.pynkin@collabora.com>
2019-07-29 02:32:28 +03:00
$(NULL)
lib: Add (private) API for checking out commits into a composefs image This supports checking out a commit into a tree which is then converted into a composefs image containing fs-verity digests for all the regular files, and payloads that are relative to a the `repo/objects` directory of a bare ostree repo. Some specal files are always created in the image. This ensures that various directories (usr, etc, boot, var, sysroot) exists in the created image, even if they were not in the source commit. These are needed (as bindmount targets) if you want to boot from the image. In the non-composefs case these are just created as needed in the checked out deploydir, but we can't do that here. This is all controlled by the new ex-integrity config section, which has the following layout: ``` [ex-integrity] fsverity=yes/no/maybe composefs=yes/no/maybe composefs-apply-sig=yes/no composefs-add-metadata=yes/no composefs-keyfiile=/a/path composefs-certfile=/a/path ``` The `fsverity` key overrides the old `ex-fsverity` section if specified. The default for all these is for the new behaviour to be disabled. Additionally, enabling composefs implies fsverity defaults to `maybe`, to avoid having to set both.
2022-06-09 18:15:29 +03:00
if USE_COMPOSEFS
Update submodule: composefs Instead of using pkg-config, etc we just include composefs. In the end the library is just 5 c source files, and it is set up to be easy to use as a submodule. For now, composefs support is disabled by default.
2023-05-23 11:31:23 +03:00
libostree_1_la_LIBADD += libcomposefs.la
lib: Add (private) API for checking out commits into a composefs image This supports checking out a commit into a tree which is then converted into a composefs image containing fs-verity digests for all the regular files, and payloads that are relative to a the `repo/objects` directory of a bare ostree repo. Some specal files are always created in the image. This ensures that various directories (usr, etc, boot, var, sysroot) exists in the created image, even if they were not in the source commit. These are needed (as bindmount targets) if you want to boot from the image. In the non-composefs case these are just created as needed in the checked out deploydir, but we can't do that here. This is all controlled by the new ex-integrity config section, which has the following layout: ``` [ex-integrity] fsverity=yes/no/maybe composefs=yes/no/maybe composefs-apply-sig=yes/no composefs-add-metadata=yes/no composefs-keyfiile=/a/path composefs-certfile=/a/path ``` The `fsverity` key overrides the old `ex-fsverity` section if specified. The default for all these is for the new behaviour to be disabled. Additionally, enabling composefs implies fsverity defaults to `maybe`, to avoid having to set both.
2022-06-09 18:15:29 +03:00
endif # USE_COMPOSEFS
Makefile-libostree.am: Work around clang issues with g-ir-scanner Work around an issue with clang-7 in Fedora 29 where the `-fstack-clash-protection` flag is not recognized. Force the compiler used by `g-ir-scanner` to `gcc`, so that the flag is recognized. Related: https://github.com/projectatomic/rpm-ostree/pull/1787#issuecomment-473971585 Closes: #1871 Approved by: jlebon
2019-06-19 20:32:00 +03:00
# XXX: work around clang being passed -fstack-clash-protection which it doesn't understand
# See: https://bugzilla.redhat.com/show_bug.cgi?id=1672012
INTROSPECTION_SCANNER_ENV = CC=gcc
Install a shared library This required a fair bit of surgery because previously ostree.h included otutil.h, but that's supposed to be a private library.
2013-07-27 03:25:07 +04:00
if BUILDOPT_INTROSPECTION
OSTree-1.0.gir: libostree-1.la Makefile
OSTree_1_0_gir_EXPORT_PACKAGES = ostree-1
OSTree_1_0_gir_INCLUDES = Gio-2.0
build: Do not include private headers in the introspection This leads to private symbols being exported. Also specify the single C header, this relies on the gir_C_INCLUDES make variable, which was introduced in gobject-introspection 1.51.5.
2023-02-08 12:24:50 +03:00
OSTree_1_0_gir_C_INCLUDES = ostree.h
Install a shared library This required a fair bit of surgery because previously ostree.h included otutil.h, but that's supposed to be a private library.
2013-07-27 03:25:07 +04:00
OSTree_1_0_gir_CFLAGS = $(libostree_1_la_CFLAGS)
OSTree_1_0_gir_LIBS = libostree-1.la
ci: Make introspection warnings fatal Closes: #965 Approved by: pwithnall
2017-06-27 01:12:33 +03:00
OSTree_1_0_gir_SCANNERFLAGS = --warn-all --identifier-prefix=Ostree --symbol-prefix=ostree $(GI_SCANNERFLAGS)
build: Do not include private headers in the introspection This leads to private symbols being exported. Also specify the single C header, this relies on the gir_C_INCLUDES make variable, which was introduced in gobject-introspection 1.51.5.
2023-02-08 12:24:50 +03:00
OSTree_1_0_gir_FILES = $(libostreeinclude_HEADERS) $(filter-out %.h,$(libostree_1_la_SOURCES))
Install a shared library This required a fair bit of surgery because previously ostree.h included otutil.h, but that's supposed to be a private library.
2013-07-27 03:25:07 +04:00
INTROSPECTION_GIRS += OSTree-1.0.gir
gir_DATA += OSTree-1.0.gir
typelib_DATA += OSTree-1.0.typelib
Fix make distcheck make distcheck was unhappy for various reasons: * headers aren't data, so use _HEADERS otherwise compilation fails * Mark the gir & typelib data as cleanfiles so they aren't left around after make clean * Don't nuke the .la file. This breaks make uninstall, leave it up to distributions to not install .la files if they don't want them. https://bugzilla.gnome.org/show_bug.cgi?id=705850
2013-08-12 18:27:42 +04:00
CLEANFILES += $(gir_DATA) $(typelib_DATA)
libostree: Move pull code into here More library work.
2013-07-10 04:14:53 +04:00
endif
Install a shared library This required a fair bit of surgery because previously ostree.h included otutil.h, but that's supposed to be a private library.
2013-07-27 03:25:07 +04:00
pkgconfig_DATA += src/libostree/ostree-1.pc
core: Use libgpgme to add GPG signatures to detached metadata for commit object Add an optional dependency on gpgme to add GPG signatures into the detached metadata, with the key "ostree.gpgsigs", as an "aay", an array of signatures (treated as binary data). The commit command gains a --gpg-sign=<key-id> argument. Also add an argument --gpg-homedir to set the GPG homedir where we look for keyrings.
2013-09-03 05:43:49 +04:00
pull: Verify commits with gpg signatures from detached metadata This uses gpgv for verification against DATADIR/ostree/pubring.gpg by default. The keyring can be overridden by specifying OSTREE_GPG_HOME. Add a unit test for commit signing with gpg key and verifying on pull; to implement this we ship a test GPG key generated with no password for Ostree Tester <test@test.com>. Change all of the existing tests to disable GPG verification.
2013-09-05 22:50:36 +04:00
gpgreadme_DATA = src/libostree/README-gpg
trusted.gpg.d: keep in the same location With the package rename from ostree to libostree, the trusted.gpg.d/ dir changed install location from /usr/share/ostree to /usr/share/libostree. Let's keep the same dir to remain compatible with existing installations that may already have keys there. Closes: #668 Approved by: cgwalters
2017-02-03 22:10:27 +03:00
gpgreadmedir = $(datadir)/ostree/trusted.gpg.d
build: 'make clean' removes parse-datetime.c and fix make dist while at it. Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2016-01-29 13:02:17 +03:00
EXTRA_DIST += src/libostree/README-gpg src/libostree/bupsplit.h \
src/libostree/ostree-enumtypes.h.template \
src/libostree/ostree-enumtypes.c.template \
libostree: mark ostree_repo_checkout_tree_at as deprecated and move its definition to a separate file. Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com> Closes: #417 Approved by: cgwalters
2016-07-27 12:11:13 +03:00
src/libostree/ostree-deployment-private.h \
libostree: add versioning macros OSTree currently provides no way to inspect the versioning information at run time, being only available at compile time through pkg-config. This is a problem for e.g. Flatpak, that needs to check whether the 'update-frequency' option is available. Checking at compile time isn't great since it's not looking for new symbols, but only if an optional feature is present. This commit, then, adds a new header that is generated at compile time, exposing OSTree's versioning information. Closes: #728 Approved by: cgwalters
2017-03-10 20:33:52 +03:00
src/libostree/ostree-repo-deprecated.h \
s390x: use 'libarchive' to modify initrd in SE case
2022-09-05 15:54:03 +03:00
src/libostree/ostree-version.h
core: Use libgpgme to add GPG signatures to detached metadata for commit object Add an optional dependency on gpgme to add GPG signatures into the detached metadata, with the key "ostree.gpgsigs", as an "aay", an array of signatures (treated as binary data). The commit command gains a --gpg-sign=<key-id> argument. Also add an argument --gpg-homedir to set the GPG homedir where we look for keyrings.
2013-09-03 05:43:49 +04:00
Support /etc/ostree/remotes.d For many OS install scenarios, one runs through an installer which may come with embedded data, and then the OS is configured post-install to receive updates. In this model, it'd be nice to avoid the post-install having to rewrite the /ostree/repo/config file. Additionally, it feels weird for admins to interact with "/ostree" - let's make the system feel more like Unix and have our important configuration in /etc. https://bugzilla.gnome.org/show_bug.cgi?id=729343
2014-05-08 17:16:36 +04:00
install-mkdir-remotes-d-hook:
build: Add missing DESTDIR Hooray for read-only bind mounts and building as non-root.
2014-05-09 17:06:59 +04:00
mkdir -p $(DESTDIR)$(sysconfdir)/ostree/remotes.d
Support /etc/ostree/remotes.d For many OS install scenarios, one runs through an installer which may come with embedded data, and then the OS is configured post-install to receive updates. In this model, it'd be nice to avoid the post-install having to rewrite the /ostree/repo/config file. Additionally, it feels weird for admins to interact with "/ostree" - let's make the system feel more like Unix and have our important configuration in /etc. https://bugzilla.gnome.org/show_bug.cgi?id=729343
2014-05-08 17:16:36 +04:00
INSTALL_DATA_HOOKS += install-mkdir-remotes-d-hook
Reference in New Issue Copy Permalink