[MPlayer-dev-eng] [PATCH] Do not read codecs.conf files by default

[Diego Biurrun]

On Sat, Jan 13, 2007 at 04:11:31PM +0100, Roberto Togni wrote:
> On Sat, 13 Jan 2007 13:02:54 +0100
> Diego Biurrun <diego at biurrun.de> wrote:
> 
> > I've had enough.
> > 
> > codecs.conf files continue doing damage in the wild.  This patch removes
> > support for reading it from default locations.  It's still possible to
> > use the -codecs-file option, so devs can put
> > 
> > codecs-file=/path/to/somewhere
> > 
> > in their config file if they wish.  The rest of the world will be spared
> > the troubles with codecs.conf for good.
> > 
> > Something similar has to be done for mencoder.c of course, I'll do that
> > at commit time if necessary.
> [...]
> 
> I'm totally against this.
> 
> MPlayer stopped installing a codecs.conf file since a long time (years).
> MPlayer rejects old codecs.conf files, atm rc1 and svn require a
> codecs.sonf file released at least with rc1.
> 
> So if somebody today has a codecs.conf file, he put it there on purpose
> and using it is the right thing to do.

The problems still exist:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=406412&repeatmerged=yes

> If some binary packages install a codecs.conf file, I don't care at
> all. We don't workaround the problems of others (and yes, user
> stupidity is not our problem).

I'll give a different reasoning: Name a reason to keep codecs.conf
loading from two different locations by default.  Or put another way, if
you were starting from scratch, would you implement it that way?

There is no reason to keep it, it simply doesn't make sense, everything
that an external codecs.conf file can be useful for (and don't forget
that you're one of the few people that routinely uses it anyway) can
easily be achieved with -codecs-file...

Diego