Merge lp:~mvo/launchpad-buildd/mvo into lp:launchpad-buildd
Status: | Work in progress |
---|---|
Proposed branch: | lp:~mvo/launchpad-buildd/mvo |
Merge into: | lp:launchpad-buildd |
Diff against target: |
106 lines (+40/-8) 1 file modified
buildlivefs (+40/-8) |
To merge this branch: | bzr merge lp:~mvo/launchpad-buildd/mvo |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Colin Watson | Needs Fixing | ||
Review via email:
|
Description of the change
This branch takes the excellent buildlivefs and adds some tweaks to make it more useful outside the buildd environment.
If that branch lands, we can consider moving it outside of the launchpad-buildd branch and into somehthing more general like livecd-rootfs or ubuntu-dev-tools so that people who want to experiment with building a rootfs. It would also provide a canonical way of building the rootfs and could superseed tools like rootstock and BuildLiveCD.
A careful review for this is needed as I'm new to the world of livefs building/buildds and may miss important setup steps that are taken before buildlivefs is called (i.e. I'm not sure if the deboostrap step I added is sufficient).
Thanks for your consideration,
Michael
Unmerged revisions
- 132. By Michael Vogt
-
fix review issues raised by Colin
- 131. By Michael Vogt
-
add a default to build-id assuming that local use is mostly sequentical
- 130. By Michael Vogt
-
refactor debootrap into _prepare_chroot() and add friendly message at the end of the build
- 129. By Michael Vogt
-
make buildlivefs more general purpose
- 128. By Michael Vogt
-
buildlivefs: if the chroot_path does not exits, bootstrap it
Thanks a lot for your review Colin. I addressed your points in r132. From reading your reply it seems like you disapprove of the idea to make this something that could live outside of launchpad-buildd. In which case the revert of the chroot creation and the build-id default make sense of course.