[Mplayer-cvslog] CVS: main mplayer.c,1.634,1.635

[Diego Biurrun]

Arpi writes:
 > > > > Very nice, just documented.  Shouldn't we also support a system-wide
 > > > > directory here? /usr/share/mplayer or /etc/mplayer?
 > > > 
 > > > i don't think so.
 > > > system-wide dirs can be written only by root, and it has no much sense to
 > > > write personal info there.
 > > 
 > > I'm with Diego on this. Imagine a mplayer installation in a bigger
 > > enviroment, where the Sysadmin wants to provide special settings for
 > > DVD and dvix.
 > 
 > heh?
 > 
 > it's not media type related, it's file related.
 > so, no way to handle dvd://.
 > you can create system-wide Maya_Gold_sucks_again.avi.conf so every user
 > watching files named Maya_Gold_sucks_again.avi with mplayer will have some
 > extra settings.
 > sorry i cannot imagine any case when it may be useful.

I was thinking along the lines of consistency.  My ideas was that if
we have something in ~/.mplayer we should offer the same functionality
system-wide.  How this makes sense for individual movies is debatable,
however, unless you want to move the movies around without having to
worry about the config files, e.g. you have a movie on CD without
config file and want certain parameters for all users.

 > esp. that since it's loaded after commandline parsing, the user has no way
 > to override it (except of renaming the file :))

That's a bug, command line should always come last and override.
Imagine a BOFH sharing his movies on a multi-user system and giving
them all config files containing

vo=null
ao=null

or just one of them, which would probably be worse ;)

I think the order should be

config file (system)
config file (user)
config file (movie)
command line

It's nice to have a per-movie config file but a pain to have to edit
it (only if you have write access as outlined above) if you wish to
override some setting for quick testing.

Diego