addpkg_svn detect version
addpkg_svn has a mode of operation where no version of the package to be added has to be specified and is figured out on the fly. This does not work correctly. For example when I've sourced development at FNAL and done an srt_setup -a in my test release ($SRT_PUBLIC_CONTEXT=/grid/fermiapp/nova/novaart/novasvn/releases/development, $CVSROOT=svn+ssh://firstname.lastname@example.org/cvs/projects/novaart/pkgs.svn)
Release development uses setup version lrwxrwxrwx 1 novasoft nova 11 Dec 20 01:56 /grid/fermiapp/nova/novaart/novasvn/releases/development/setup -> ../../setup, will check that out
Adding package "setup" to ".".
svn co svn+ssh://email@example.com/cvs/projects/novaart/pkgs.svn/tags/lrwxrwxrwx 1 novasoft nova 11 Dec 20 01:56 /grid/fermiapp/nova/novaart/novasvn/releases/development/setup -> ../../setup//setup setup
svn: invalid option character: >
Type 'svn help' for usage.
svn checkout failed.
#2 Updated by Kanika Sachdev almost 6 years ago
But obviously this won't work for tags before now since the you'd be using the version of addpkg_svn in $SRT_PUBLIC_CONTEXT, and not the one in head :(
So you would have to specify the tag before this date, so do "addpkg_svn package_name tag_name", whereas, here on, you can just do "addpkg_svn package_name" and it will automatically figure out what to checkout.