Henrik Nordström wrote:
ons 2010-05-26 klockan 21:43 +1200 skrev Amos Jeffries:
I was hoping that after your autoconf rework it would become a simple
matter of making the initial default setting for most option tests a
simple variable assignment of the value (auto or no) as set by this option.
Not sure it matters.
./configure --help list a lot of --disable-XXX options people interested
in small builds may use.
Having a general "minimal" configure option does not make much sense as
even the embedded ones very likely want some things enabled such as http
violations.
Regards
Henrik
The embeded use-case is only half the pro list. Whats bumped it up to
being worth mentioning was this case:
We hit a v6 "bug" in Debian and Ubuntu where the package failed to have
explicit --enable-ipv6 and one of the 15 or so package build hosts had
broken v6 support. This resulted in some release packages being
v6-disabled and others not. QA was not pleased, nor were the users whose
v6 support broken for ten days.
Debian and maybe other distro have a policy that the same configure
options MUST produce consistent featured packages. For now this is been
resolved partially by explicitly configuring all features to required.
Auto-enable is great for encouraging feature use in self-builds, but for
distros its just added work for the downstream maintainers.
Amos
--
Please be using
Current Stable Squid 2.7.STABLE9 or 3.1.3
