On Fri, Jun 20, 2008 at 4:20 AM, Carlo Calica <[EMAIL PROTECTED]> wrote: > This email is to kick off development of the 015 LiveCD. We've been > waiting for GCC 4.3.1 to ship and that has happened now. I know that > Jonas has built a toolchain and some packages. What else is needed to > fill out ChrootCompile? Lucas, could you chime in? Once > ChrootCompile is setup we can start building packages.
The last known problems were fixed last friday, so BatchChrootCompile should do its job fairly nice now. We just need to create a new tree under calica.com on which SetupChrootCompile will download its initial base packages. Apart from that, things are pretty much set. In the meantime, I was just talking to Jonas about the "share"/"lib" problem -- many packages suffer from ugly hacks in order to work fine in our tree (take CUPS, DirectFB and the ALSA family of applications as an example). Directories.conf is now capable of recognizing different prefixes for compilation and installation, so we should be able to compile our packages with prefix=/System/Index, and then install them at /Programs/Foo/Version. That'll require a few changes to SandboxInstall, though, as re-evaluating parameters passed to make. I'd love to see this happening for 015, as it'll be one more step towards ViewFS. And we'll finally get rid of "Shared" and its sibling, the share symlink. What do you guys think? > We need an area of the wiki for 015 design docs. First up is which > packages belong in stage 1 developement. Eventually we'll need pages > for stages 2 and 3. Unless someone beats me I'll try to put up a page > soon. > > I'd like to reorg the packages store for 015. Basically put livecd, > official, chrootcompile inside a 015 directory. X.1 and later would > be livecd-015.1 as dirs under 015. We'd do the same with 014 but > provide 'legacy' symlinks. To do this we need a bit of coordination > from mirror operations. I'd also like to see how mirrors are chained > documented somewhere. I don't know if calica.com or kundor.org is > master for instance. Such organization will be really welcome, as they'll allow one to configure different profiles for ChrootCompile. > I was hoping to be able to separate where BuildLiveCD gets its package > list from its version but I haven't had the chance yet. As a > workaround I think I'll do a branch on BuildLiveCD for 014 and keep > trunk 015. Any advice for doing branches on svn? I'd just rename gobolinux-packages/livecd/ to gobolinux-packages/livecd-014 and start over using livecd-015. That'll force us to create a Settings file for BuildLiveCD, which is certainly a better thing to do. There are a bunch of minor changes to do in BuildLiveCD, most of them related to Settings, and this first step will help a little to make them happen. > Eventually we should do an IRC meeting but I'd like to build up some > momentum on list first. Yes. I believe I'll be still pretty busy for the next days, but that should change in the first days of july. I cannot promise I'll be available for any meetings before that, but I'll certainly try to join you there. -- Lucas powered by /dev/dsp _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
