[MPlayer-dev-eng] deterministic builds

[Enrico Weigelt]

* Attila Kinali <attila at kinali.ch> [2003-12-20 12:17:56 +0100]:

<snip>
> Ugh... you know what you are doing ?
> if you treat preX as 1.0.0.X then you actualy make 1.0 (the release)
> an earlier release than any pre version.

No, 1.0 will be mapped to someting like 1.0.0.65535. The mapping itself
does not really matter as long as it is consistent.

<snip>
> > This should describe the software's structure on the highest possible level,
> > so many many tools, can work on it, i.e. for completely automated builds
> > and constraint tests, etc.
> > (The tree-like modeling perhaps reminds a little bit on borland's 
> > C++ builder UI)
> 
> Dunno... but it sounds quite complicated to use.
Not really. It will make things easier, since you simply write down
which modules, sourcefiles, etc your software consists of.
You simply dont have to care about makefiles, installing, etc anylonger.

<snip>
> Oh.. good luck then. The work which you want to do requires >20 different
> mplayer packages, maybe even more than 100. 
Doesnt matter, since these different builds are generated automatically
as they're required. Its the task of the installer to choose the right 
configuration. 


cu
-- 
---------------------------------------------------------------------
 Enrico Weigelt    ==   metux IT services

  phone:     +49 36207 519931         www:       http://www.metux.de/
  fax:       +49 36207 519932         email:     contact at metux.de
  cellphone: +49 174 7066481
---------------------------------------------------------------------
 Diese Mail wurde mit UUCP versandt.      http://www.metux.de/uucp/