[MPlayer-cvslog] CVS: main configure,1.1029,1.1030

Jan Knutar jknutar at nic.fi
Fri Jul 22 10:06:08 CEST 2005

On Thursday 21 July 2005 22:40, The Wanderer wrote:

> > That is not my position. Autodetection is fine as default. It should
> > however still be possible to disable components without having to
> > uninstall them before compiling mplayer.
> And it is (the --disable-foo options). What I inferred from your
> statement, however, was that "MPlayer should not automatically bloat
> itself up as much as possible",

Ah sorry, that is not what I meant.

> and in the current context that appears 
> to mean "MPlayer should not automatically compile in things without
> asking" - which means "autodetection should not be default". If I'm
> misreading you, I'd love to know how.

I find the current behaviour of automatically compiling in whatever configure
finds available quite good. It simplifies things greatly for newcomers, but I have
seen people asking "what do I need to --enable for blah" where blah is something
like xvid, divx, optimizing, etc. Renaming these options into --force, would perhaps
clear that misunderstanding amongst certain user groups, that they need to --enable
lots of random stuff to get the most out of mplayer on their system.

Just because --enable would be removed and renamed into --force, I wanted to put
in a note to keep --disable still around, in case someone wants to build a smaller
binary, or prevent libraries that are buggy to be linked in (for example libartsc on my
system seems to install so many exit handlers that don't play nice together with
mplayer, sdl or anything more complex than a trivial hello world).

I apologize if I expressed it unclearly and hope this has cleared up confusion a bit...

> I am, however, glad to know that this is more likely to be a problem of
> semantics than an actual disagreement...

More information about the MPlayer-cvslog mailing list