[MPlayer-dev-eng] configure --force-option (was --enable-gif)

[The Wanderer]

Torinthiel wrote:

> On Mon, Sep 06, 2004 at 07:47:17AM -0400, The Wanderer wrote:
> 
>> (All of this is merely my own opinion.)
>> 
>> Torinthiel wrote:
>> 
>>> On Mon, Sep 06, 2004 at 12:44:14AM -0400, Adrian wrote:

>>> auto-yes runs autodetection, and notifies if it has failed. So
>>> it's new behaviour, not comparable to anything we know ;)
>> 
>> How is this new behaviour? How does it differ from
>> no-argument-provided autodetection, as that takes place now?
> 
> That it makes more verbose any autodetection failures.

That wasn't specified, but okay.

> Two options have been suggested, either ./configure fails when
> something with auto-yes is not detected, or add a new field
> containing not autodetected modules that had auto-yes to the summary
> printed at end of ./configure's work.

Ideally I'd prefer to be able to choose one or the other at runtime;
failing that, I think the latter would be better for my purposes, but I
can see how having it fail out would be preferable in some cases.

>> IOW: If some form of this version of the proposal gets adopted,
>> 'yes' would be set by passing --enable-*, not by --force-* or
>> anything of that sort. What to use to set 'auto-yes' remains open
>> for discussion.
> 
> How about --enable stays --enable, and auto-yes is set by --request.

That's acceptable as far as I'm concerned.

> BTW This whole will require a MAJOR change in --help message.
> Probably a change of structure, not just adding some text.

But of course. If and when a final structure for the configure flags
gets settled upon, I'll see if I can come up with something, but I'll
probably wind up just criticizing and suggesting improvements on a base
provided by others. (That's all I've done so far, mostly...)

-- 
       The Wanderer

Warning: Simply because I argue an issue does not mean I agree with any
side of it.

A government exists to serve its citizens, not to control them.