[MPlayer-dev-eng] configure force enable all

[Dominik 'Rathann' Mierzejewski]

On Thursday, 28 July 2005 at 00:13, Ivan Kalvachev wrote:
> On 7/26/05, Reimar Döffinger <Reimar.Doeffinger at stud.uni-karlsruhe.de> wrote:
> > Hi,
> > On Tue, Jul 26, 2005 at 09:21:22PM +0300, Ivan Kalvachev wrote:
> > > Look at the attachment and tell me what do you think.
> > >
> > > The code is not finished yet (actually not sure if it works at all),
> > > but you should get the idea.
> > 
> > Well, not really. Maybe describe in a few words what you want to
> > achieve...
> > E.g. setting _default_no=auto will not owkr I think, since most of the
> > options that are disabled by default simply have no autodetection...
> > There is at least a high risk of breaking things I think.
> 
> OK, one day passed.
> I would like to summarize the prevous flamewars.
> 
> The current configure uses the following meaning for --enable--foo:
> If option is autodetected by default, --enable will force it.

Yes.

> if option is disable by default, --enable will autodetect it.

Not really. These options are on/off, there's no autodetection.

> configure script autodetects most of the stuff, so --enable usually
> mean --force.
> Of course if somebody wants to build an minimum featued mplayer (free
> of bloat;), he have to use multiple --disable-foo options. With adding
> new options this list grows.

Yes. I know about this. I'm packaging the stuff.

> I have created 2 new options --disable-all and --enable-all. The first
> one disables all optional features. The second one enables
> autodetection for all usually disable options.
> On the end of second configure flamewar all had agreed that these
> *-all options are good idea.

I didn't and I disagree. I'm quite happy the way things are now.

Regards,
R.

-- 
MPlayer RPMs maintainer: http://rpm.greysector.net/mplayer/
"I am Grey. I stand between the candle and the star. We are Grey.
 We stand between the darkness ... and the light."
        -- Delenn in Grey Council in Babylon 5:"Babylon Squared"