a284b64479
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 |
||
|---|---|---|
| .. | ||
| fetch-journal.sh | ||
| multitest.py | ||
| overlay.sh | ||
| sync.sh | ||
| test-initramfs.sh | ||
| test-layering-basic.sh | ||
| test-layering-gpg.sh | ||
| test-layering-local.sh | ||
| test-layering-non-root-caps.sh | ||
| test-layering-relayer.sh | ||
| test-layering-rpmdb.sh | ||
| test-layering-scripts.sh | ||
| test-layering-unified.sh | ||
| test.sh | ||