Merge lp:~vorlon/launchpad-buildd/image-targets into lp:launchpad-buildd
Status: | Merged |
---|---|
Merge reported by: | Colin Watson |
Merged at revision: | not available |
Proposed branch: | lp:~vorlon/launchpad-buildd/image-targets |
Merge into: | lp:launchpad-buildd |
Diff against target: |
47 lines (+13/-0) 2 files modified
buildlivefs (+6/-0) debian/changelog (+7/-0) |
To merge this branch: | bzr merge lp:~vorlon/launchpad-buildd/image-targets |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Colin Watson (community) | Needs Fixing | ||
Review via email: mp+316648@code.launchpad.net |
Description of the change
The ubuntu-cpc project is unusual in that for a single project, it produces multiple image outputs, each of which can be fairly time consuming to build. By default we want the ubuntu-cpc build to produce the full set of relevant images for the architecture, but I would find it useful to be able to specify (especially when iterating during development) that I only want a subset of images produced.
This branch proposes a syntax for passing that information through launchpad-buildd into the hook scripts via the environment. See https:/
This is distinct from subarch, as we could legitimately have both a kernel subarchitecture type and a cloud target specified as part of a single build; also, we can't legitimately pass multiple subarch options to a single build.
It is also distinct from --image-format, which is mapped to live-build's --chroot-filesystem within livecd-rootfs.
This is basically fine, but I'm afraid you've missed a layer of marshalling here. I'm assuming you want to be able to set an "image_targets" list from Launchpad, and for that to work you also need to change lpbuildd/livefs.py to marshal those into --image-target arguments to buildlivefs.