Code like rpm-ostree generates disk images directly. In order to ensure SELinux labeling is correct, it currently has a helper program that runs over the deployment root, then over the whole disk and to only set a label if none exist. In order to make it easier to write installers such as Anaconda without having them depend on rpm-ostree (or whatever other build-server side program), pull in the helper code here. |
||
|---|---|---|
| doc | ||
| embedded-dependencies | ||
| manual-tests | ||
| packaging | ||
| selinux | ||
| src | ||
| tests | ||
| .gitignore | ||
| .gitmodules | ||
| COPYING | ||
| Makefile-boot.am | ||
| Makefile-decls.am | ||
| Makefile-libostree-defines.am | ||
| Makefile-libostree.am | ||
| Makefile-ostree.am | ||
| Makefile-otutil.am | ||
| Makefile-switchroot.am | ||
| Makefile-tests.am | ||
| Makefile.am | ||
| Makefile.dist-packaging | ||
| README-historical.md | ||
| README.md | ||
| TODO | ||
| autogen.sh | ||
| configure.ac | ||
| ostree.doap | ||
README.md
OSTree is a tool for managing bootable, immutable, versioned filesystem trees. While it takes over some of the roles of tradtional "package managers" like dpkg and rpm, it is not a package system; nor is it a tool for managing full disk images. Instead, it sits between those levels, offering a blend of the advantages (and disadvantages) of both.
For more information, see: