Merge ~cjwatson/launchpad:livefs-build-pocket into launchpad:master
Status: | Needs review |
---|---|
Proposed branch: | ~cjwatson/launchpad:livefs-build-pocket |
Merge into: | launchpad:master |
Diff against target: |
59 lines (+20/-3) 2 files modified
lib/lp/soyuz/model/livefsbuildbehaviour.py (+8/-2) lib/lp/soyuz/tests/test_livefsbuildbehaviour.py (+12/-1) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Launchpad code reviewers | Pending | ||
Review via email: mp+373803@code.launchpad.net |
Commit message
Allow livefs build metadata to override the default build pocket
Description of the change
This makes it possible, for example, to distinguish the case of building a livefs using tools from -updates but with contents from the release pocket from the case of building a livefs using tools from -updates and contents from -updates.
The use case here is that at the moment buildd images are built with tools from -updates but with contents from the release pocket. I'd like it to be possible to build buildd images with contents from -updates as well, since we could use those for builds against -updates and it would save a good deal of time at the start of each build.
We've ended up in a bit of a compatibility corner due to some unfortunate past decisions (mostly by me), and this is the least bad solution I can think of. launchpad-buildd and livecd-rootfs will also need some work to support this, but this design allows it to be done in a somewhat backwards-
This is essentially the same as https:/