>>Tim Armes said:
>>> What I need then, is an svnlastchangedversion command.
>>>
>>> Any ideas?
>>
>>I have an idea, but I need to understand how your build process works. How
do
>>you inject the build number?
>>
>>I inject the blessed release number in the subversion Mandrake RPMs
>>(subversion binaries I maintain) on the fly based on the tag they came
from.
>
>I don't currently do it, so I can pretty much implement any solution.
>
>I can also do a search on the output from svn info, grab the last changed
>number and use that. I was hoping that a simpler solution existed.
I take that back, it isn't a solution. svnversion looks at the contents of
the working copy and add an M if the version has been modified. This is
useful in the case where a developer commits his or her changes and then
compiles without updating first.
An svninfo on the working copy simply reports the last changed version of
the directory, which would be less than the revision number of the working
copy...
###########################################
This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange.
For more information, connect to http://www.F-Secure.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Nov 13 16:22:57 2003