I don't know if I understand it correctly but can installation process insert version number from ./bzr/branch/last-version directly. And update script will check if database value is the same. If database value is lower then in .bzr folder then it need to update if is equal it ok, and it can be sanity check if it's higher then it should show message that you need to upgrade files on disk (but it will never happen unless someone mess with database)
On Sun, 29 Jan 2012 00:00:14 +0100 Roger Martín <rg1...@gmail.com> wrote: > Hi folks!: > > I'm working on update system ( see > https://blueprints.launchpad.net/aikiframework/+spec/need-robust-update-system > ). > > Aiki need a way to provide aiki version and revision. Now version is > defined in bootstrap.php as constant, and version is read from > ./bzr/branch/last-version if exist. > > I want create a AIKI_ROOT/configs/version.txt, with Aiki version and > revision, for example. > 0.8.26 1043 > > During installation process this numbers will be inserted in > database. If a admin updates all aiki files, the version stored in > database will be different that existing in file; aiki knows a > upgrade must be done. > > It's not necessary to update the revision number in every push only > when the revision changes database or requires 'corrections' in > widget. > > Other reason to separate aiki version from bootstrap, is that aiki > can have auxiliary applications (installer, upgrade, recovery crash) > than can read the information without booting aiki. > > Sorry, i know there are a lot of discussion of version and revisions, > but now, there is a new needs. > > Roger -- Jakub Jankiewicz twitter: @jcubic www: http://jcubic.pl _______________________________________________ Mailing list: https://launchpad.net/~aikiframework-devel Post to : aikiframework-devel@lists.launchpad.net Unsubscribe : https://launchpad.net/~aikiframework-devel More help : https://help.launchpad.net/ListHelp