Re: Ubuntu live filesystem builds moved to live-build
On 06/14/2011 10:46 AM, Colin Watson wrote: That would be lovely, thanks. Here's a patch, with text from http://www.debian.org/misc/children-distros: applied, thanks. ftr: if the wiki is world-readable through git just like the manual. if you want to change it in future, you can do it directly. Right - in fact I was uncomfortable with even the Kubuntu hook. I'm not sure how to represent that well; it doesn't fit nicely into the --parent-distribution/--distribution scheme, because it's not a full-archive derivative but more a different package selection out of the same archive. when i've reworked the hook thingies (#630395), it can be nicely integrated. -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: Ubuntu live filesystem builds moved to live-build
On Tue, Jun 14, 2011 at 08:52:19AM +0200, Daniel Baumann wrote: > On 06/14/2011 12:38 AM, Colin Watson wrote: > > I've moved Ubuntu's live filesystem build process over from our original > > custom shell script in livecd-rootfs to the newer live-build system from > > Debian (formerly called live-helper). > > nice; would you mind having ubuntu listed on > live.debian.net/project/downstream ? That would be lovely, thanks. Here's a patch, with text from http://www.debian.org/misc/children-distros: diff --git a/project/downstream.mdwn b/project/downstream.mdwn index af589d1..db5ce5d 100644 --- a/project/downstream.mdwn +++ b/project/downstream.mdwn @@ -246,6 +246,16 @@ More information: * [Homepage](http://www.supergrubdisk.org/rescatux/) +## Ubuntu + +[Ubuntu](http://www.ubuntu.com/) is a Linux distribution that starts with the breadth of Debian and adds regular releases (every six months), a clear focus on the user and usability (it should "Just Work", TM) and a commitment to security updates with 18 months of support for every release. Ubuntu ships with the latest GNOME and KDE releases as well as a selection of server and desktop software that makes for a comfortable desktop experience off a single installation CD. + +Ubuntu is sponsored by [Canonical Ltd.](http://www.canonical.com/) + +More information: + + * [Homepage](http://www.ubuntu.com/) + ## Voyage [Voyage](http://linux.voyage.hk/) is best run on a x86 embedded platforms such as PC Engines ALIX/WRAP and Soekris 45xx/48xx boards. > > * If necessary, there are various hook script facilities that you can > >use: for example, scripts in config/chroot_local-hooks/ are run in > >the chroot near the end of the chroot build process. Try to keep > >this to a minimum, though; I'm trying to avoid using hook scripts in > >builds for Ubuntu proper, as it would be better for live-build to do > >the right thing out of the box without the need for hooks. > > let me reaffirm: we'll include any ubuntu modification happily, hooks > really should only be used for specific private modification, any > 'generic' image (like debian or ubuntu; in contrast to a specific image > for a specific institution with hardcoded local defaults) should be > buildable by using live-builds defaults for that distribution. that way, > we can make sure that it's as easy and simple as possible for people to > build customized images on top of debian or ubuntu. Right - in fact I was uncomfortable with even the Kubuntu hook. I'm not sure how to represent that well; it doesn't fit nicely into the --parent-distribution/--distribution scheme, because it's not a full-archive derivative but more a different package selection out of the same archive. > >now, the only hook script I'm using is one to remove icon-theme.cache > >from Kubuntu images. > > this, and the other two outstanding additions (apt-xapian, mlocate) are > blocked until the internals are a bit updated in live-build to scale > nicer for more distributions and more distro specific hooks (adding it > right now would just clutter it some more). anyhow, that should happen > within the next 1 or at latest 2 weeks (#630395). Yes, I noticed the blocking bug you added. Thanks. -- Colin Watson [cjwat...@ubuntu.com] -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: Ubuntu live filesystem builds moved to live-build
On 06/14/2011 12:38 AM, Colin Watson wrote: > I've moved Ubuntu's live filesystem build process over from our original > custom shell script in livecd-rootfs to the newer live-build system from > Debian (formerly called live-helper). nice; would you mind having ubuntu listed on live.debian.net/project/downstream ? > my goal is, > if at all possible, to be using an unpatched version of live-build from > Debian by the time we release Oneiric. shouldn't be a problem :) don't hesitate to let me know whenever you need an upload in order to trigger a sync. > * If necessary, there are various hook script facilities that you can >use: for example, scripts in config/chroot_local-hooks/ are run in >the chroot near the end of the chroot build process. Try to keep >this to a minimum, though; I'm trying to avoid using hook scripts in >builds for Ubuntu proper, as it would be better for live-build to do >the right thing out of the box without the need for hooks. let me reaffirm: we'll include any ubuntu modification happily, hooks really should only be used for specific private modification, any 'generic' image (like debian or ubuntu; in contrast to a specific image for a specific institution with hardcoded local defaults) should be buildable by using live-builds defaults for that distribution. that way, we can make sure that it's as easy and simple as possible for people to build customized images on top of debian or ubuntu. >now, the only hook script I'm using is one to remove icon-theme.cache >from Kubuntu images. this, and the other two outstanding additions (apt-xapian, mlocate) are blocked until the internals are a bit updated in live-build to scale nicer for more distributions and more distro specific hooks (adding it right now would just clutter it some more). anyhow, that should happen within the next 1 or at latest 2 weeks (#630395). Regards, Daniel -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Ubuntu live filesystem builds moved to live-build
I've moved Ubuntu's live filesystem build process over from our original
custom shell script in livecd-rootfs to the newer live-build system from
Debian (formerly called live-helper). Thanks in particular to Daniel
Baumann for guidance and for speedy upstream patch integration, and to
LaMont Jones for deployment assistance.
This only affects Oneiric and later releases. Live filesystem builds
for previous releases will continue to use livecd-rootfs.
Developers who have not needed to modify livecd-rootfs in the past
should have no more need to modify it now than before; it still uses
tasks in much the same way to decide which packages should be installed.
However, people working on Ubuntu live filesystems will need to know how
the new build process is laid out. I needed to have somewhere to put
configuration anyway, so I repurposed the livecd-rootfs package for
that, using auto/* files along the lines of
http://live.debian.net/manual/en/html/managing-a-configuration.html. I
expect that the exact details may change here as we gain more experience
with live-build. Briefly, the current way to reproduce an Ubuntu live
filesystem build is to do this in a scratch directory:
Once only:
$ mkdir -p auto
$ ln -sf /usr/share/livecd-rootfs/live-build/auto/* auto/
Each time:
$ export PROJECT=ubuntu SUITE=oneiric ARCH=i386
$ sudo lb clean
$ lb config
$ sudo lb build
There were a handful of changes in ubiquity 2.7.6 to cope with slight
differences in manifest files and sources.list generation. These only
make a difference if you're producing installable live CDs.
If you are modifying the live build process for Ubuntu, please remember
that we are now working with an upstream codebase: the days of hacking a
couple of special-purpose lines into livecd-rootfs are over. While we
do have three outstanding patches against upstream right now, they have
all been submitted as Debian bug reports (if it's any guide, there were
seven outstanding when I started drafting this mail!), and my goal is,
if at all possible, to be using an unpatched version of live-build from
Debian by the time we release Oneiric. Instead of perpetrating
Ubuntu-specific hacks, please consider these alternatives:
* live-build has lots and lots of options, and in many cases you can do
what you need by tweaking those.
* Patch live-build to do what you need, send your patch as a Debian
bug, and engage in upstream discussion if necessary. Note that, if
need be, you can guard your code with [ "${LB_MODE}" = ubuntu ].
* If necessary, there are various hook script facilities that you can
use: for example, scripts in config/chroot_local-hooks/ are run in
the chroot near the end of the chroot build process. Try to keep
this to a minimum, though; I'm trying to avoid using hook scripts in
builds for Ubuntu proper, as it would be better for live-build to do
the right thing out of the box without the need for hooks. Right
now, the only hook script I'm using is one to remove icon-theme.cache
from Kubuntu images.
If you have any questions about the Ubuntu integration here, please ask.
Cheers,
--
Colin Watson [cjwat...@ubuntu.com]
--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
