On Mon, 2006-29-05 at 15:39 -0400, Youness Alaoui wrote: > Yes, but the file is not read... you should read the svn_rev file, if it > doesn't exist, then try the svn command, if it doesn't exist, then use the > $::date The problem with this at the moment is that $::date variable is always used with a release. So we should probably replace this with a new variable called ::revision that will be updated just like $::date is now.
As for the svn_rev, we could do it like cvs_date, at least for now. Have it updated regulary with a cron job. I was looking through out the .svn directory and found a file that keeps the current revision embeded in bunch of XML. I would first like to figure out how the file is structured though so it dosn't change with different versions of svn. About the command line checking of revision. If it is a svn build, then the svn_rev file should be present. I don't think that there would be a need to start a shell and run the svn command. What are others views on this? I started working on this (web and client parts) on my computer. Will commit it when everything will be finished. > also, the revision number is not a date, so watch out for that, it may > crash the bug reporting if the DB assumes it should receive a date, not a > string... > > KaKaRoTo > > On Mon, 29 May 2006 15:15:00 -0400, Sander Hoentjen <[EMAIL PROTECTED]> > wrote: > > > On Tue, 2006-05-30 at 00:19 +1000, Arieh Schneier wrote: > >> Aren't you assuming that the user has svn support installed and is > >> using the > >> svn version? What about all the users that use the packages, or the > >> tarball? > >> > > Yes I am asuming that. In packages and the tarball there should be this > > info included. > > > _______________________________________________ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
