Hi, and this time it's even working :)
Let's repeat... If you are using a version control system to store your live-helper config directory, you should not store the generated files config/* in it, but only save which arguments you passed to lh_config and your own files that you put into the config/*/* directories. If you would store them in the vcs, you would have troubles over time, as the format of the generated config files may change. If you use the (almost) stable interface to generate the config, the lh_config tool, you can avoid that completely and always have a working and up2date config without manually updating/touching it. In order to ease this, lh_config from ive-helper in git (which gets uploaded to unstable this weekend) does check for a scripts/config.sh file. If present, it executes it instead. Same applies to scripts/clean.sh for lh_clean. ...and the workflow would be: 1. create a git repository 2. add a .gitignore file, example at http://git.debian.org/?p=debian-live/config-daniel.git;a=blob;f=.gitignore; 3. add a scripts/config.sh with your complex lh_config call/options, example at http://git.debian.org/?p=debian-live/config-daniel.git;a=blob;f=scripts/config.sh; 4. commit that 5. when you actually build your live system, you checkout your repository in your build directory 6. run lh_config (any additional argument is optional and will be appended to the lh_config call in scripts/config.sh). 7. lh_build I think this is almost sane. Cluebats, as usual, are welcome. Regards, Daniel -- Address: Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist Email: daniel.baum...@panthera-systems.net Internet: http://people.panthera-systems.net/~daniel-baumann/ -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
