[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Sharing of sub-projects and tagging

From: Cyril Margorin <comargo_at_gmail.com>
Date: Sat, 15 Nov 2008 01:21:22 +0300


Our company starts migrating from <censored> VSS to SVN so I'm new to
SVN and even has not much experience with CVS.
I'm trying to find a way, to share the sub-projects, that are common
for our some of our projects (like a custom user controls, or helper
classes for multi-threaded operations, or custom build tools).

I've found that property svn:externals work fine for me, until I start
tagging of project.
As I see, if I tag the project, the svn:externals for tagged version
of project still points to HEAD version of shared sub-project, and any
changes in sub-project, made after tagging will be reflected in frozen
(tagged) copy. So I have to manually change the svn:externals property
to pin current REV of sub-project. Do it manually is not good idea
(who wants to do something manually if you have a computer? :) )

From other side, branching the sub-project to number of projects will
require programmer to
1) make changes in main trunk, that is somewhere else, but not in this project,
2) merge changes to all project that uses this sub-project.
- So it is another problem, that programmer should handle manually.

I prefer the first way, but, as I see, I need to put a hook-script,
that will be called on any copy command, and change the svn:externals
property to current revision.

The quiestions are:
Is this problem already solved/described somewhere?
Could someone point me to solution (script) that does it?


Cyril Margorin
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-11-14 23:21:45 CET

This is an archived mail posted to the Subversion Users mailing list.