> I have made some progress in the live DDL building process. > I have now an iso of about 800 Mo with 53 DDL packages built.
Mmm, we'll have to find a way to remove 100 MB then, quite a lot… You can install synaptic or whatever package manager in a running DDL to sort packages by size and list those that are the most space consuming. This is a good start point to let us think about how to perform such size reduction. > I have removed for testing : > - lxsession-lite (replaced by lxsession) OK. > - apertium-dbus (removed for testing) To be investigated, it is used by the Apertium GUI to talk with the command line client. > - lxpanel (removed for testing) > - pcmanfm (removed for testing) Quite annoying, even if this doesn't prevent DDL from functioning, this removes interesting features. > > Alright, this may increase the build time a bit due to slower disk > > access. > > Yhanks for this advice. How long is your build process lasting? On a recent Debian laptop it lasts 15 min. for a 700MB image file. > The branch live/experimental/squeeze/ will be create soon. I saw this work has already started :). I have to tell you my own convention to comment SVN operations: “section/directory: description”. * section is the root directory in the SVN tree, eg. 'live' or 'lang'. * directory is the latest directory of the file concerned by the operation, eg. 'rewrite' for file “live/trunk/config-l10n/rewrite/01dummy”. * description is the traditional SVN comment This way it is easier to understand what part of code is concerned when reading SVN logs. Of course when the latest directory has a generic name, I'm using its parent, eg. 'gcompris' for “lang/trunk/apps/education/gcompris/po/fr.po”. Finally when the commit is concerning several files, just try to use the largest common path to determine section and directory. > Well, deeper analysis will be needed to make the squeeze port. > Not so simple. Yes, and DDL system configuration files need revisiting. But don't worry I'll help you as much as possible :). > - 53 packages seems okay > - 3 need analysis > - 1 may be replaced/removed Not so dramatical finally. > I still have to fix : > - apartium (apartium-udev complain about apartium not found) Maybe just add apertium to the package list. Please also check that this bug is reported to Debian too since it seems to be a missing package dependency. > - apartium is not found in config/chroot_local-hooks/20-set-dash-shell.sh It sounds logical if it could not be installed. This hook script restores bash as the shell for apertium since it cannot work with dash (which is a much lighter shell than bash). > - grub splash screen is not translated It's not grub but syslinux ;), I made trials with grub but switched back to syslinux. Maybe they changed the default English texts. This kind of translation is performed by hook scripts during the build process, they change files in build/chroot or build/binary. Look into config-base/binary_local-hooks/ for the script 10-set-syslinux.sh. > - login session are not translated Usually this is happening when there is a problem at boot while creating users. A live system is creating its users at each boot. There are 2 scripts involved in this translation: * config-base/chroot_local-includes/usr/share/initramfs-tools/scripts/live-bottom/90session-users → creates/renames users during LiveCD boot * config-l10n/rewrite/90session-user → translates texts in the former script before the CD build process is started (rewrite scripts, see below) > - application are in english (DDL packages were built in "all" and > live DDL was built in "fr") Boot parameters that control the system language are located in files directly in the config-base directory. I have rewrite scripts in config-l10n/rewrite that rewrite these configuration files with the localized parameters. To understand how all of this works, you have to know that the build process is the following: 1. global LH parameters are copied from config-base into build/config 2. translation files (PO, TS and so) are copied into build/config/chroot_local-includes 3. localized files are copied from config-l10n/overwrite into build/config 4. some global LH parameters are modified by rewrite scripts located in config-l10n/rewrite 5. LH builds the CD invoking hook scripts during the build process, hook scripts that can have been modified by rewrite scripts for translation purposes… Please check boot parameters in the files in build/config/ and compare with the syslinux boot configuration file that should lay in build/binary/syslinux/ after the CD is built. Don't hesitate to tell me if some technical points are still vague. Cheers, JM. _______________________________________________ Doudoulinux-dev mailing list [email protected] https://mail.gna.org/listinfo/doudoulinux-dev
