rpm-ostree/ci
Colin Walters a284b64479 ci: Use FAHC for build container
Conceptually: we're going to move rpm-ostree and ostree at the same
cadence most of the time; for both releases *and* for git master.
The problem so far has been the latter part.  Reusing FAHC
for the build gets us half of the problem.

The other trick I realized we can do - just pull ostree out from the build
container. This avoids fetching it from the internet, and makes my workflow for
hacking on both nicer - I just `sudo make install` in my build container for
ostree.

It's tempting to make the whole thing symmetric and require `sudo make install`
for rpm-ostree and not do the insttree thing but...perhaps after.

Closes: #758
Approved by: jlebon
2017-05-01 19:10:05 +00:00
..
build-check.sh ci: Delete dockerfile, move to common scripts, consolidate gcc/clang 2017-04-28 21:17:18 +00:00
build.sh ci: Use FAHC for build container 2017-05-01 19:10:05 +00:00
libbuild.sh ci: Delete dockerfile, move to common scripts, consolidate gcc/clang 2017-04-28 21:17:18 +00:00