I just noticed the fact that --enable-all also works for all --with-xyz by
being mailed about it. IMHO there should be an --with-all. This because
we have a clear difference between --enable-xy and --with-xy. This
difference should hold for --enable-all, too.
regards
marcus
At 17:28 05.04.2003, Peter Neuman wrote:
Hello,
"Marcus Börger" marcus.boerger@t-online.de:
I just noticed the fact that --enable-all also works for all --with-xyz by
being mailed about it. IMHO there should be an --with-all. This because
we have a clear difference between --enable-xy and --with-xy. This
difference should hold for --enable-all, too.which is actually differentiated between --with-xyz and --enable-xyz?
--enable-xyz is for ectension not depending on external libraries and
--with-xyz
is for extensions depending on external libraries.
marcus
At 19:48 05.04.2003, Jani Taskinen wrote:
I just noticed the fact that --enable-all also works for all --with-xyz by
being mailed about it. IMHO there should be an --with-all. This because
we have a clear difference between --enable-xy and --with-xy. This
difference should hold for --enable-all, too.I never advertized --enable-all. It was just a side-effect of
--disable-all and should never be used by anyone.I removed the --enable-all from the configure help now.
I'll disable it fully later..
Jani, IMO --enable-all is a good thing but it shouldn't apply to --with
extensions. So perhaps we should have an undocumented --with-all
and make --enable-all what it is supposed to.
marcus
Jani, IMO --enable-all is a good thing but it shouldn't apply to --with
extensions. So perhaps we should have an undocumented --with-all
and make --enable-all what it is supposed to.
--with-all is rather unrealistic, isn't it? Some of the --with flags are
mutually exclusive as well so you can never have a real --with-all.
-Rasmus