Nathan Brink wrote:
> Henrik K wrote:
>> On Sun, Mar 01, 2009 at 04:11:08PM -0500, Nathan Brink wrote:
>>
>>> I don't like it when other programs do this because it departs from the
>>> normal output of ./configure scripts.
>>>
>> What exactly are you doing with the output that it bothers you and where is
>> this "standard" defined?
>>
> The standard is defined by the implementation of autoconf which many
> projects use. Most will just run and give the output of ./configure to
> the screen. It bothers me when people write wrappers for ./configure,
> like ./Config for unrealircd, or when ./configure is messed with much in
> other ways. People should be able to read ./configure --help and
> purposefully enable and disable the optional packages, etc. that they
> want. ./configure should die when these are unsatisfiable; the test that
> wasn't satisfied is printed right before it dies, making it easy to
> locate. Then the user will know what package he is missing/what's wrong
OK ! What about what do some packages using, not wrappers but,
"standard" autoconf/automake features (such as AC_MSG_NOTICE). I call
them standard as they don't do anything not natively provided by
autoconf/automake architecture.
Some examples of this kind of (very professional) software, which I
think at the moment :
xemacs, gnuplot, pcre, dovecot, curl
There are surely many other more.
But sure, it's a question of "colours and tastes". 8-)
<snip>
--
---------------------------------------------------------------
Jose Marcio MARTINS DA CRUZ http://j-chkmail.ensmp.fr
Ecole des Mines de Paris
60, bd Saint Michel 75272 - PARIS CEDEX 06
mailto:jose-marcio.mart...@mines-paristech.fr
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml
