FTWCA storing config/ in VCS
Hi,
for those who care about storing their live systems config directories
in a version control system, this is the now recommended way of doing it.
Eventhough it is a good idea to store config directories in version
control, this has had (up to now) one big disadvantage which was
discussed some weeks ago on irc and also on the mailinglist: you're in
need of keeping track about renames of LH_* variables in config/* since
the only (almost) stable API of live-helper are the flags of lh_config,
and because lh_config needs to be called with all parameters at once and
without having a previous populated config arround in order to be
deterministic about dependent config options (e.g. the default values
for LH_INITRAMFS does differ between casper and live-initramfs depending
on if LH_DISTRIBUTION is set to etch or not). just calling lh_config
wouldn't touch or update your already existing config.
This quite sucks, and therefore lh_config from live-helper in git now
reads out a config.cfg file (on the same directory level as config/, not
inside config/) which can contain the config flags to be passed to
lh_config (in addition to any manually given on the command line).
This means, you should store config.cfg and config/*/* inside git (or
your other VCS of choice), add config/* to gitignore (as well as binary*
chroot* source* etc.), and always, if you clone the repository, run a
lh_config to populate config/* files followed by a lh_build to actually
built the image.
Regards,
Daniel
--
Address: Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist
Email: daniel.baumann@panthera-systems.net
Internet: http://people.panthera-systems.net/~daniel-baumann/
Reply to: