Nice-to-have fix for autogen.sh

[Segher Boessenkool]

>>> o autogen.sh is only used by maintainers - official distributions
>>> would have a configure (and Makefile) ready to use, so no need for
>>> autogen.
>>
>> That is not an argument for either way.
>
> Well, I think it quite restricts the scope of the people who are  
> expected to find that having an autogen that runs configure is an  
> annoyance.

And exactly analogously for people who find _not_ running it an
annoyance!

>>> o maintainers have a fairly good idea of the options they want to  
>>> have
>>> by default during development (--enable-maintainer-mode,  
>>> debugging on,
>>> etc.) so they might as well enable them while accepting extra
>>> configure options through the use of $*.
>>
>> I don't know about you, but I do not usually want any of the options
>> that are enabled by default (except for maintainer mode some of the
>> time).
>
> I don't know about you, but when I'm one of the lead developers of  
> a project, I tend to want to set options that I think will benefit  
> both myself and others by default.

Sure.

> I strongly believe that the default for any developers who wants to  
> contribute to libusbx should be to have logging.

Why only for developers though?

Run-time configurable logging sure would help :-)

>> If you're building a lot, you probably should run some ./build
>> anyway ;-)
>
> Why should I, when the default autogen.sh is just fine?

Most people at least want a --prefix if they build a lot (since
they typically have many versions installed).

>> Let's go with the principle of least surprise, so do what most
>> projects do (or the most authoritative ones).
>
> Let's go with the principle of what will be most helpful for our  
> users.

That is the same thing, in general.


Segher