Ben Laurie wrote:
If it does nothing unless a file is specified, why not enable by default?
to avoid silent growth in the set of code built into somebody's server... when does somebody have to add "--disable-foo" to create a build compatible with what they had with the 1.3.(n-1) release?
(I don't feel very strongly about it; it just seems like the right approach to me; over and out)
I guess if its disabled by default it doesn't hurt much to have it also not compiled by default.
Cheers,
Ben.
-- http://www.apache-ssl.org/ben.html http://www.thebunker.net/
"There is no limit to what a man can do or how far he can go if he doesn't mind who gets the credit." - Robert Woodruff
