On Tuesday 10 June 2008, 22:21:41, Daniel Baumann wrote:
Marco Amadori wrote:
Yes, I put it there because I think it was wanted, since ${LH_CONFFILE}
is sourced just below.
the idea is to have the system-wide defaults to be used, but as soon as
any custom conffile, any existing config/*
Marco Amadori wrote:
I do not agree for command line parameters, it will really surprise me if I
specify both a conffile and a custom parameter via command line option and
the latter will be overruled by the config file.
so where's the disagreement? i did excately write that. however, code
On Wednesday 11 June 2008, 15:30:41, Daniel Baumann wrote:
Marco Amadori wrote:
I do not agree for command line parameters, it will really surprise me
if I specify both a conffile and a custom parameter via command line
option and the latter will be overruled by the config file.
so
Marco Amadori wrote:
I was meaning that, now I'm fine.
thanks for bringing it up.
--
Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist
Email: [EMAIL PROTECTED]
Internet: http://people.panthera-systems.net/~daniel-baumann/
Juergen Fiedler wrote:
In HEAD, it looks like ${SYSTEM_LH_CONFFILE} and ${LH_CONFFILE} are
read after Local_arguments [EMAIL PROTECTED] is called (which happens after
the
local conf files are sourced). Would that not make the system defaults
override the command line options and the local
On Tuesday 10 June 2008 19:00:39 Juergen Fiedler wrote:
In HEAD, it looks like ${SYSTEM_LH_CONFFILE} and ${LH_CONFFILE} are
read after Local_arguments [EMAIL PROTECTED] is called (which happens after
the
local conf files are sourced). Would that not make the system defaults
override the
Marco Amadori wrote:
Yes, I put it there because I think it was wanted, since ${LH_CONFFILE} is
sourced just below.
the idea is to have the system-wide defaults to be used, but as soon as
any custom conffile, any existing config/* or any parameter for the same
variable is given, it will be
7 matches
Mail list logo
