Go to file
Simon McVittie ca899ccfd3 tests: use our own generated libtool, not the one in $PATH
libtoolize creates a version of libtool for the right architecture
in $(top_builddir), which is guaranteed to be present, and is
guaranteed to match what we are compiling (even during
cross-compilation).

Packaging systems sometimes separate /usr/bin/libtool, which is
specific to one architecture, from the libtool development files
such as libtoolize and ltmain.sh, which are architecture-independent.
For example, in Debian, libtool_*_all.deb contains the files necessary
to libtoolize a package and is depended on by the dh-autoreconf package,
but libtool-bin_*_amd64.deb (or whatever architecture) contains
/usr/bin/libtool and is not normally necessary to depend on.

Signed-off-by: Simon McVittie <smcv@debian.org>

Closes: #367
Approved by: cgwalters
2016-06-26 21:31:35 +00:00
apidoc refs: resolve conflict between local/remote repos 2016-06-23 19:52:26 +00:00
bsdiff@1edf9f6568 bsdiff: change submodule location 2015-03-26 23:33:07 +01:00
build-aux Add infrastructure for "make syntax-check" 2015-01-30 15:27:36 +01:00
buildutil tap-test: clean up temporary test directories as intended 2016-03-31 14:22:06 +00:00
contrib/golang contrib: indent golang code using only tabs instead of both tabs and spaces 2016-04-07 12:25:24 +00:00
docs manual: Discuss mirroring 2016-06-17 14:14:08 +00:00
libglnx@a6d08657aa libglnx porting: delete temp files on failure of file creation 2016-06-16 19:18:47 +00:00
man commit: Update manpage to reflect --editor 2016-05-25 18:37:47 +00:00
manual-tests Fix make syntax-check 2016-03-01 10:08:25 -05:00
packaging build: Introduce --with-dracut=yesbutnoconf 2016-05-01 10:25:19 +00:00
src pull: Write commitpartial files for local imports too 2016-06-24 15:21:38 +00:00
tests entry_pathname_test_helper: these tests need extended attributes 2016-06-26 21:15:36 +00:00
.gitmodules bsdiff: change submodule location 2015-03-26 23:33:07 +01:00
.travis.yml Remove empty new lines at the EOF 2016-04-07 12:25:24 +00:00
CONTRIBUTING.md Rewrite manual in mkdocs 2016-01-28 09:31:37 -05:00
COPYING COPYING: Update to latest FSF with current address 2014-01-16 10:22:30 -05:00
GNUmakefile Add infrastructure for "make syntax-check" 2015-01-30 15:27:36 +01:00
Makefile-boot.am build: Introduce --with-dracut=yesbutnoconf 2016-05-01 10:25:19 +00:00
Makefile-decls.am Makefile: Move to AM_DISTCHECK_CONFIGURE_FLAGS 2016-05-12 12:25:08 +00:00
Makefile-libostree-defines.am build: Install new autocleanups header 2016-05-19 13:04:06 +00:00
Makefile-libostree.am build-sys: Make libostree-1.so depend on the symbol file 2016-06-24 21:06:56 +00:00
Makefile-man.am admin: Add an `unlock` command, and libostree API 2016-03-23 11:09:09 -04:00
Makefile-ostree.am lib: Use sd_journal directly (optionally) 2016-06-21 18:24:17 +00:00
Makefile-otutil.am lib: Use sd_journal directly (optionally) 2016-06-21 18:24:17 +00:00
Makefile-switchroot.am Add support for mkinitcpio 2013-10-24 14:27:49 -04:00
Makefile-tests.am tests: use our own generated libtool, not the one in $PATH 2016-06-26 21:31:35 +00:00
Makefile.am build: Allow ostree to use g_autoptr on its types internally 2016-05-17 21:13:20 +00:00
README-historical.md README: Just link to wiki, move most of it to README-historical.md 2014-01-20 18:00:09 -05:00
README.md README: x/xdg-app/flatpak/ 2016-05-13 14:01:37 +00:00
TODO Fix repeated words. 2015-01-30 15:27:36 +01:00
autogen.sh autogen.sh: rely on VPATH for submodules' Makefile-*.am.inc 2016-06-13 00:23:03 +00:00
cfg.mk small cleanups 2016-04-08 18:43:18 +00:00
configure.ac configure: Turn on -Wempty-body 2016-06-22 16:10:01 +00:00
git.mk Use git.mk 2016-04-07 12:49:40 +00:00
maint.mk tests: prefix invocation of ostree with where missing 2015-11-16 11:07:55 +01:00
mkdocs.yml docs: Add a section on repository management 2016-03-29 14:10:24 +00:00
ostree.doap doap category infrastructure 2014-07-31 11:26:32 +02:00

README.md

OSTree

New! See the docs online at Read The Docs (OSTree)


OSTree is a tool that combines a "git-like" model for committing and downloading bootable filesystem trees, along with a layer for deploying them and managing the bootloader configuration.

OSTree is like git in that it checksums individual files and has a content-addressed-object store. It's unlike git in that it "checks out" the files via hardlinks, and they should thus be immutable. Therefore, another way to think of OSTree is that it's just a more polished version of Linux VServer hardlinks.

Features:

  • Atomic upgrades and rollback for the system
  • Replicating content incrementally over HTTP via GPG signatures and "pinned TLS" support
  • Support for parallel installing more than just 2 bootable roots
  • Binary history on the server side (and client)
  • Introspectable shared library API for build and deployment systems

This last point is important - you should think of the OSTree command line as effectively a "demo" for the shared library. The intent is that package managers, system upgrade tools, container build tools and the like use OSTree as a "deduplicating hardlink store".

Projects using OSTree

rpm-ostree is a tool that uses OSTree as a shared library, and supports committing RPMs into an OSTree repository, and deploying them on the client. This is appropriate for "fixed purpose" systems. There is in progress work for more sophisticated hybrid models, deeply integrating the RPM packaging with OSTree.

Project Atomic uses rpm-ostree to provide a minimal host for Docker formatted Linux containers. Replicating a base immutable OS, then using Docker for applications meshes together two different tools with different tradeoffs.

flatpak uses OSTree for desktop application containers.

GNOME Continuous is a custom build system designed for OSTree, using OpenEmbedded in concert with a custom build system to do continuous delivery from hundreds of git repositories.

Building

Releases are available as GPG signed git tags, and most recent versions support extended validation using git-evtag.

However, in order to build from a git clone, you must update the submodules. If you're packaging OSTree and want a tarball, I recommend using a "recursive git archive" script. There are several available online; this code in OSTree is an example.

Once you have a git clone or recursive archive, building is the same as almost every autotools project:

env NOCONFIGURE=1 ./autogen.sh
./configure --prefix=...
make
make install DESTDIR=/path/to/dest

More documentation

New! See the docs online at Read The Docs (OSTree)

Some more information is available on the old wiki page: https://wiki.gnome.org/Projects/OSTree

Contributing

See Contributing.