keremet/rpm-ostree
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

README.md: Update for split repositories

Browse Source
This commit is contained in:
Colin Walters 2014-05-10 13:58:29 -04:00
parent f3b1bbfcd8
commit ed113d4c0c
1 changed files with 12 additions and 24 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

36
README.md
View File

@ -5,16 +5,19 @@ This tool takes a set of packages, and commits them to an
[OSTree](https://wiki.gnome.org/Projects/OSTree) repository. At the
moment, it is intended for use on build servers.
Using rpm-ostree
----------------
Major changes since 2014.8
--------------------------
There are two levels; the core "rpm-ostree" command takes a set of
packages and commits them to an OSTree repository.
The previous major release of this program contained within it an
"autobuilder" codebase which had significant functionality beyond just
composing trees, such as creating VM disk images and running
smoketests.
The higher level rpm-ostree-autobuilder parses a "products.json" which
generates potentially many filesystem trees. It also has code to
generate disk images and run smoketests.
Since that time, the other functionality has moved to:
https://github.com/cgwalters/rpm-ostree-autocompose
This program now only commits trees to a repository, using "treefiles"
which are very simple JSON input data.
Installing and setting up a repository
--------------------------------------
@ -51,12 +54,11 @@ Once you have that done, choose a build directory. Here we'll use
# mkdir repo
# ostree --repo=repo init --mode=archive-z2
Running rpm-ostree
------------------
The core "rpm-ostree" takes as input a "treefile". There is a demo
one in `doc/demo-treefile.json`.
The core "rpm-ostree" takes as input a "treefile". See examples in
`doc/treefile-examples`.
# rpm-ostree treecompose --repo=/srv/rpm-ostree/repo --proxy=http://127.0.0.1:8123 sometreefile.json
@ -67,17 +69,3 @@ this case) - otherwise we you will download the packages for each
treecompose.
You can export `/srv/rpm-ostree/repo` via any static webserver.
Running the autobuilder
-----------------------
The autobuilder instead takes as input a `products.json` which
generates *multiple* treefile internally. Try this:
# ln -s /path/to/rpm-ostree.git/fedostree/products.json .
# rpm-ostree-autobuilder
That will automatically poll every hour for changes in the RPMs
referenced by the `products.json` file, commit them to the
`/srv/rpm-ostree/repo`, and generate cached disk images in
`/srv/rpm-ostree/images`.