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

Re: tagging and keeping the tree structure: an existential question

From: Hilco Wijbenga <hilco.wijbenga_at_gmail.com>
Date: Thu, 7 Aug 2008 11:28:33 -0700

Just some random comments...

On Thu, Aug 7, 2008 at 6:16 AM, Michele Zamparelli <mzampare_at_eso.org> wrote:
> Dear Subversion folks,
> I am noticing an unexpected behavior in the way the Eclipse plugins support
> Subversion and in particular the usage of tags.
> While one might argue that this would then be more suitable for an eclipse
> plugin mailing list, the underlying question is, maybe, to which extent and
> how SVN is supposed to support a specific feature of CVS.
> The feature I am talking about is the fact that once you check-out a file
> with CVS using a specific tag you retrieve
> a) the file with the correct tagged version
> b) the file in the correct location in the CVS repository tree.
> It seems to me that the Eclipse plugins do not account for this function
> (which is supported by the corresponding CVS plugins)
> Maybe my assumptions on the usage of SVN are wrong and I wanted to know if
> the general SVN users community has comments to make.
> Here the problem description:
> we use the word "module" to identify a well defined directory structure
> like:
> M/src
> M/include
> M/object/
> M/lib
> Suppose that M1 and M2 are two modules in the tree-like SVN repository,
> which could look like:
> trunk/alpha/beta/M1 assigned to person P1
> trunk/alpha/beta/M2 assigned to person P2
> (any depth is allowed, depending on the circumstances)

Why not alpha/beta/M1/trunk and alpha/beta/M2/trunk? If necessary, you
might want to consider using svn:external to link various modules
together in a separate project.

> Assume we're using Eclipse with the Subversive plugin (I believe the other
> behaves just the same, though I am not sure)
> Suppose P1 wants to tag M1 with the name "MyTag" (or any other symbolic
> name, for that matter).
> M1 is normally handled as a single "project" in Eclipse.
> Subversive only allows the following tag to be created:
> tags/MyTag/M1 whereas what would be desired is:
> tags/MyTag/alpha/beta/M1

With the scheme above that would simply be alpha/beta/M1/tags/MyTag, I
assume the plugins support that?

> In other words in our community it is fairly important that when a symbolic
> name is communicated, the user of such release can extract the code from the
> repository and find it in the customary location, i.e. according to the tree
> structure which is present in the trunk.
> Now, I know very well that to SVN trunk and tags mean nothing special, but
> is this still not the case that a CVS feature is, at the very least,
> cumbersome to achieve?
> Notice that such a behavior can be obtained with the command line, although
> in an error-prone way, by doing something like:
> svn mkdir -m "creating tag MyTag" svn://URL/tags/Mytag
> svn mkdir -m "creating tag MyTag" svn://URL/tags/MyTag/alpha
> svn mkdir -m "creating tag MyTag" svn://URL/tags/MyTag/alpha/beta
> and finally
> svn copy -m "tagging MyTag" M1 svn://URL/tags/MyTag/alpha/beta

I would do something like

mkdir -p tags/MyTag/alpha/beta
svn add tags/MyTag
svn copy ...
svn commit

That's not so error prone.

> Are we the only one who have this problem?
> Does SVN suggest another way to proceed?
> Is requesting this functionality from the plugins the right way to proceed?
> thanks for any help
> Michele


To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-08-07 20:29:11 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.