On Sun, Oct 12, 2008 at 01:26:35PM +0200, Daniel Baumann wrote:
> Tzafrir Cohen wrote:
> > I maintain the configuration directory under version control. The old
> > values that lh_config once generated make little sense to me. Many of
> > them have changed over time anyway.
>
> that's manual overriding of variables then.
>
> > Or is lh_config the only supported interface? and manual tweaks are not
> > allowed?
>
> yes. you should *either* only change settings with lh_config *or* know
> what you do/keep the config consistent yourself.
We had a small chat on that yesterday, so it can help to clear some
misunderstandings:
The simplest test case here is running 'lh_build' in an empty directory
(no configuration). This will fail at lh_chroot_install-packages because
the list of packages to install includes the two:
${LH_UNION_FILESYSTEM}-modules-2.6-amd64
auto
To which both Daniel Bauman and Chris Lamb claimed that an empty
configuration is invalid, because it has not been blessed by running
lh_config on it.
I consider this a bug. In order to resolve this I would suggest to set
some variable in lh_config before calling Set_defaults . That would
allow Set_defaults to make more informed decisions and specifically
avoid those two issues.
I'm not actively working on debian-live nowadays. So I guess I won't be
get to actually write this soon. I hope someone will beat me to it.
--
Tzafrir Cohen
icq#16849755 jabber:[EMAIL PROTECTED]
+972-50-7952406 mailto:[EMAIL PROTECTED]
http://www.xorcom.com iax:[EMAIL PROTECTED]/tzafrir
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
