Robert Osfield wrote:
I do understand what your are looking for, but I don't agree it's
clearer... having two tags for the same thing, and copying over the
top of the same tag repeatidly. I consider this misuse of the svn
repository.
Same feeling here...
What you could do is create a new directory called "latest" next to the
trunk, branches, tags, etc directories. Then you set two svn:externals
on that directory, one named "stable" pointing to the latest released
stable revision (the same on that was tagged), and one named
"development" pointing to the latest released development version.
When a new release is made the appropriate property of the "latest" dir
would need to be updated. On the end-user side an "svn update" within
his/her checkout of the "latest" directoy would update if needed.
At least, I think this should work, would need to try it out though.
Paul
Robert.
On Tue, Oct 7, 2008 at 4:18 PM, Mathieu MARACHE
<[EMAIL PROTECTED]> wrote:
Hi Robert,
I'm not talking about a symbolique link. It's just a another copy,
just plain subversion copy :
svn copy -m"tagging 2.7.2" http://.../trunk http://.../tags/osg-2.7.2
svn copy -m"updating developer release" http://.../tags/osg-2.7.2
http://.../tags/osg-latest-dev-release
and then tagging next release would be the same :
svn copy -m"tagging 2.7.3" http://.../trunk http://.../tags/osg-2.7.3
svn copy -m"updating developer release" http://.../tags/osg-2.7.3
http://.../tags/osg-latest-dev-release
Only if I wanted to have the the latest developer release checked out,
if I had :
svn co http://.../tags/osg-latest-dev-release osg-devel
in the 2.7.2 days it would then update to the 2.7.3 (when it's
tagged) with an svn update
Is it a bit clearer ?
Mathieu
2008/10/7 Robert Osfield <[EMAIL PROTECTED]>:
Hi Mathieu,
What you are asking for is symbolic link to the latest tags rather
than an actual tag. I don't know if svn is capable of doing
something like this. Perhaps the webserver could do some url
direction.. I have no clue on this stuff so I'll leave it to svn
server and web server experts to dive in with recommendations.
Robert.
On Tue, Oct 7, 2008 at 3:07 PM, Mathieu MARACHE
<[EMAIL PROTECTED]> wrote:
Hi,
This is probably only directed to Paul Martz and Robert Osfield, but
here it goes : I was wondering if you could add two more tags on the
subversion repository that would be tagging the latest stable and
development releases and evolving with them. For example :
OpenSceneGraph-latest-stable-release would be the same as OpenSceneGraph-2.6.1
OpenSceneGraph-latest-dev-release would be OpenSceneGraph-2.7.2 as of
today and moving to OpenSceneGraph-2.7.3 sooner or later.
My aim is to setup (my) continuous integration servers to build
automatically the latest version of each branch.
--
Mathieu
_______________________________________________
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
_______________________________________________
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
_______________________________________________
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
_______________________________________________
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
_______________________________________________
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
