Hi, On Fri, Mar 16, 2012 at 03:07:24PM +0200, Samuli Seppänen wrote: > Having as much stuff as possible disabled by default and then enabled > selectively _feels_ cleaner. But I'm fine with either approach.
I think the default should be "what most people are using".
- enable crypto and ssl
- enable lzo
> Personally, I don't think we'll get many complaints if lzo is disabled
> by default. As Alon points out, this is not the only thing packagers
> need to adjust to, so they expect things to work differently. Hopefully
> this translates to them paying some attention while doing the builds :).
It would annoy me a lot to have to remember to add --enable-lzo whenever
I build, and I see no compelling reason to change the default.
About the only time you want to disable lzo is if you need to save code
space, like on very small embedded systems - and that's the exception,
not the common case.
(And I don't see any reason why "the packages that people ship" should
be built with non-default options, except "the default options do not
make sense, so all the packagers need to change the options")
gert
--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany g...@greenie.muc.de
fax: +49-89-35655025 g...@net.informatik.tu-muenchen.de
pgp1OHOTl1veX.pgp
Description: PGP signature
