On 06/01/2012 20:24, Ben Bolker wrote:
I'm trying to keep debugging of a development package relatively sane.
I see that some packages manage to incorporate what appears to be
Subversion (SVN) revision information in the package description; for
example,
library(MASS)
sessionInfo()$otherPkgs$MASS$Revision
[1] "$Rev: 3016 $"
which looks like an auto-generated revision number.
On the other hand, the rgl package (for example) appears to manually
encode the SVN revision in the package number:
library(rgl)
sessionInfo()$otherPkgs$rgl$Version
[1] "0.92.829"
I'd love an automatic strategy, if possible, so I can be lazy about
updating the DESCRIPTION file every time I commit a change to SVN ...
I searched the R extensions manual (and the r-forge manual), but I'm
sure I could have missed something ...
The Subversion book? The MASS/DESCRIPTION file has
gannet% svn proplist DESCRIPTION
Properties on 'DESCRIPTION':
svn:keywords
Note this only tracks the version when DESCRIPTION is changed, not what
anything else is updated. But then I change the DESCRIPTION file
immediately before release.
Or can people suggest other useful strategies for keeping track of
which development (micro-)version a random user might be working with?
thanks,
Ben Bolker
______________________________________________
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
--
Brian D. Ripley, rip...@stats.ox.ac.uk
Professor of Applied Statistics, http://www.stats.ox.ac.uk/~ripley/
University of Oxford, Tel: +44 1865 272861 (self)
1 South Parks Road, +44 1865 272866 (PA)
Oxford OX1 3TG, UK Fax: +44 1865 272595
______________________________________________
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
