Details
-
Type:
New Feature
-
Status: Done/Fixed
-
Priority:
Trivial
-
Resolution: Fixed/Completed
-
Affects Version/s: 2.2.2
-
Fix Version/s: 2.2.3
-
Component/s: Core CiviCRM
-
Labels:None
Description
As I try to relate CiviCRM tarballs to repository versions, I can't find the Subversion revision number anywhere in the code. Would it be possible to add the $Revision SVN keyword property somewhere, say in civicrm-version.txt or so?
Thanks in advance – Walt
Attachments
Activity
The catch is, civicrm-version.txt is not kept in the repository (so can't be managed by Suversion), while xml/version.xml is managed, but is not being shipped in the tarballs (so putting $Revision$ in there won't make you happy, I assume).
Do you need a single place that would work the same for both svn checkouts and tarballs, or would putting the revision in either of the above (or both) fix this problem for you?
can we add it to civicrm-version .txt? we can append it to the end
so basically
$DM_VERSION Drupal PHP5 SVN_REVISION
should not be too hard, snce we can get the svn revision from svn info (which we used to do)
Yes, but that file isn't hosted in the repository, so we can't use $Revision$ for (and it won't be possible to check in an svn-based install). That said, 'fixed' in r21129. 
Batch move to verification
assigning for 3.0 QA
Tested & verified in r23282.
For what it's worth, you can always check it with svn info:
shot@devielle:~$ svn info http://svn.civicrm.org/civicrm/tags/tarballs/2.2.1
[...]
Last Changed Rev: 20438
Last Changed Date: 2009-03-25 13:56:36 +0100 (Wed, 25 Mar 2009)
CiviCRM 2.2.1 was built in r20438, so off of the state of branches/v2.2 at the time of that revision.