[MPlayer-dev-eng] codecs.conf versioning

[D Richard Felker III]

On Tue, May 21, 2002 at 02:41:27PM +0200, Alex Beregszaszi wrote:
> <20020520135514.A24731 at lumen>; from joey at yunamusic.com on Mon, May 20, 2002 at 01:55:14PM -0500
> > Hello, 
> > 
> > On Mon, May 20, 2002 at 03:30:18AM +0200, Arpi wrote:
> > > Hi,
> > > 
> > > What about adding a version number to the codecs.conf file, and check
> > > for this number in mplayer at the startup?
> > > it shouldn't require up-to-minute codecs.conf, but we could increase the
> > > version number at incompatible changes (when the new version is REQUIRED
> > > to work)
> > > 
> > > something like:
> > > version 123
> > > should be ok, right?
> > 
> > > the only question is: what numbering sheme to be used?
> > > we could use a counter, starting from 1 and increasing every time when
> > > a big change is done, or use something like mplayer version number +
> > > subversion? like 0.90-3 ? later may look better but hard to parse and handle.
> > 
> > What about a format like YYYYMMDD for the sake of CVS versions?
> I prefer YYYYMMDDN - N stands for number/version like in bind, to support
> more breaking changes in a day - it's possible by mplayer (pre)releases ;)

This is bad if the number is signed -- we'll overflow the year in 2145 or so. :)

Rich