[MPlayer-cvslog] r20560 - trunk/configure

[Diego Biurrun]

On Thu, Nov 02, 2006 at 09:02:05PM +0100, Roberto Togni wrote:
> On Wed, 1 Nov 2006 20:00:36 +0100
> Diego Biurrun <diego at biurrun.de> wrote:
> 
> [...]
> > > 
> > > WTF?
> > > Shouldn't option renamings be discussed on the list? (MPlayer
> > > policy, paragraph 4)
> > 
> > MPlayer options - yes, configure options - hardly.
> 
> The result is the same: breaking existing code for no reason. So I
> don't see why that should be treated differently.

This only affects the people who build MPlayer themselves and use these
options.  We have never worried about backwards-compatibility of
configure options in the past ...

> > > This broke (at least) all my building scripts.
> > 
> > I'm aware of this, it broke my build scripts as well.  I'm overhauling
> > the codecs directory handling anyway, making semantic changes visible in
> > this way is not a bad idea IMO.
> 
> This has nothing to do with it, always enabling binary loader
> compilation (even if you have no codecs installed) has nothing to do
> with the selection of the codec path. The old naming was not implying
> anything about enabling or disabling the loader, and that's true also
> for the new names.

It is related.  The behavior of configure wrt to binary codecs has
changed and the semantics of the codecs directories has changed as well.
In the past e.g. reallibdir might point to the location of a RealPlayer
installation while now it points to the path for our binary codecs.

Diego