Compilation defaults [Was: Re: W2K Domain Login Problem with 2.2.0]

[David Lee]

On Mon, 23 Apr 2001, Jeremy Allison wrote:

> I'm coming to the conclusion that Simo came up with the
> best idea. We compile with pam on systems that support it,
> but ship with an smb.conf "use pam = no" by default.
> 
> That way people who want to descend into the undocumented
> hell :-) that is a pam module can do so in full knowledge
> of what they're getting into.... :-).

Generalising this onto one of my hobby-horses...

There are various other "--with-XYZ" options that are long-established. 
Could we also consider compiling these in by default, and using a default
"no" in "smb.conf"?

There are so many of these options (for good reason, of course, while
under development), and this principle (defaults compile:on, smb.conf:off)
would both simplify the end-user's "configure" labyrinth, and also ease
the task of the creators and maintainers of RPMS, PKGs, etc.

Two examples close to my own heart:
1. utmp:  the "utmp = {yes|no}" switch is already there, defaulting "no".

2. quotas: all we'd need to do is to add the smb.conf switch.

I'm sure there must be others...

-- 

:  David Lee                                I.T. Service          :
:  Systems Programmer                       Computer Centre       :
:                                           University of Durham  :
:  http://www.dur.ac.uk/t.d.lee/            South Road            :
:                                           Durham                :
:  Phone: +44 191 374 2882                  U.K.                  :