lib/version.php needs to include svn version

Next topic

Author	Message
Paul Forsyth	Tuesday 13 May 2003 8:17:04 am It would be nice if an extra line was added to lib/version.php to show the svn version in use. Im not sure about relevant svn directives but i assume there is something that will text replace some variable in a text file, much like cvs does with $$ directives. Of course, this doesn't need to be present in a full release. Paul
Bård Farstad	Saturday 19 June 2004 12:20:12 pm There is a feature in svn to replace variables with the version number. However it only updates the file if it's actually commited. So this will not work. Mabye there is a way to configure svn to force update of this number even if other files are commited. --bård Documentation: http://ez.no/doc
Paul Forsyth	Tuesday 29 June 2004 12:00:54 pm I remember with CVS you could perform defined actions upon a commit. Here we could update lib/version.php. This is a little heavy though for regular checkins. An alternative would be to put the $id$ string into the changelog, and if some 'unstable/unreleased' flag is set the setup/info view could query the id string from the changelog. The changelog is regularly updated and may be an alternative to lib/version.php which would be used for 'stable/releases'. paul -- http://www.visionwt.com

Author

Message

Tuesday 13 May 2003 8:17:04 am

It would be nice if an extra line was added to lib/version.php to show the svn version in use.

Im not sure about relevant svn directives but i assume there is something that will text replace some variable in a text file, much like cvs does with $$ directives.

Of course, this doesn't need to be present in a full release.

Paul

Bård Farstad

Saturday 19 June 2004 12:20:12 pm

There is a feature in svn to replace variables with the version number. However it only updates the file if it's actually commited. So this will not work.

Mabye there is a way to configure svn to force update of this number even if other files are commited.

--bård

Documentation: http://ez.no/doc

Paul Forsyth

Tuesday 29 June 2004 12:00:54 pm

I remember with CVS you could perform defined actions upon a commit. Here we could update lib/version.php. This is a little heavy though for regular checkins.

An alternative would be to put the $id$ string into the changelog, and if some 'unstable/unreleased' flag is set the setup/info view could query the id string from the changelog. The changelog is regularly updated and may be an alternative to lib/version.php which would be used for 'stable/releases'.

paul

--
http://www.visionwt.com