> Thanks for the tips, it the third solution that I choose.

Great, this is the solution we will use in the end.

> I use a fresh squeeze installation in a VirtualBox.

Alright, this may increase the build time a bit due to slower disk access.

> I have corrected all needed files for DDL squeeze (LH 1.x -> LB 2.x).

Good job! Please request for joining our team on Gna then put these files onto 
the experimental branch, say “live/experimental/squeeze/”.

> DDL Live parts build with just some dependencies fixes (removed and
> added)

Please post a diff to let me know what changes occurred ;). Or start by copying 
the trunk tree into experimental so that SVN will do the diff for you and me.

> I have made a backup with for experimental.
> For now the packages needing some fixes are lxsession-lite (seem to
> be
> replaced by lxsession) and apartium-dbus (dev dependencie to fix)
> I just removed for testing purpose.

I have a netbook at home which I recently migrated from Lenny to Squeeze. I 
noticed the change in lxsession. I also noticed that lxlauncher now has 
different naming for its configuration file “launcher.menu”. Note that 
lxlauncher is patched in DDL to allow users specify their own menu file. The 
patch certainly needs to be ported to this new version.

> I have to made the packages loccaly and the add them to the live
> building process in local packages folder.

You're right, our Debian repository only declares packages for Lenny. We need 
to list which packages can be safely moved to Squeeze as is, which ones need 
porting DDL patches to their official Squeeze version, which ones can be 
removed from our repository since the Squeeze version can have solved our 
issues.

> The problem with pysycache was that I use a VB mount points and a
> symlink cannot be done on thi filesystem.
> 
> Pysycache successfully compile now.

Cool :).

> I will make a greater working partition for compilation need.

I have a dedicated partition for package caching (2 GB), expect the building 
process to require the size of the ISO file plus an uncompressed version of its 
filesystem (~ 2GB), then add extra space if you want to store some CD's. Note 
also that RAM free space plays a role in the building process duration since 
files can be cached in RAM (or not!) for the deb files, the ISO filesystem and 
the final ISO file… If you want everything in RAM, well, should need around 3 
GB!

Cheers,
JM.

_______________________________________________
Doudoulinux-dev mailing list
[email protected]
https://mail.gna.org/listinfo/doudoulinux-dev

Reply via email to