Julian Foad wrote:
> ...
>> How about just displaying a warning message at the end of the
>> configure output, like you already do when there isn't a local
>> copy of Berkeley DB installed?
>>
>> That way, if someone configured with --with-apache and didn't
>> realize that they really wanted --with-apxs, they'll see something
>> like:
>>
>> Warning: You used --with-apache, which is normally only used
>> for statically compiling Subversion into Apache.
>>
>> Use the --with-apxs option to build a dynamically
>> loadable Apache module.
>>
>> Thoughts?
>
>
> Print the warning just because I used an unusual option? Yuck. No.
> Software that prints a warning about what I requested just because some
> other people mis-use it makes me angry.
I'd like to see what happens when someone cuts your off in traffic...
Seriously, the focus of this change seems to be around clarifying
the difference between --with-apache and --with-apxs, apparently
because some people, even experts, get confused about this the first
time they build Subversion (I fell into that category the first time
I built Subversion, BTW...)
If the assumption is that users normally want a dynamic module
instead of a static build, then what does it hurt to display a
warning message or hint at the end, just as you already do for
Berkeley DB (the warning message will appear even if I use
--without-berkeley-db...) I'm not talking about creating something
as annoying as "clippy", just checking for common configuration
errors and letting the user know about it.
--
______________________________________________________________________
Michael Sweet, Easy Software Products mike at easysw dot com
Internet Printing and Document Software http://www.easysw.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Oct 6 22:02:44 2005