Re: tag copy directory convention

>>So I would create /tags/Cpp/myProject2, in this example
>No, assuming you want to name the tag "foo", it would be
>/tags/foo/Cpp/myProject2
Hmmm...not sure what 'foo' would be.
I was thinking that the first time i do this i would have:
/tags/Cpp/myProject2/version_1.0/
and then next time:
/tags/Cpp/myProject2/version_2.0/

>I'd recommend that you rearrange your directory layout, but that may well
>not be feasible for you.
not really, no.

-------------------------------------------

On 6/20/2006 5:48 PM, Al Lelopath wrote:

                 The usual convention is that your main development occurs in a directory
named /trunk, and tag foo is a snapshot of the whole trunk directory copied
into /tags/foo.

Your organization is close to this, except that you call the /trunk
directory /code. So I'd create /tags at the same level as /code, and put
your tags there.
So I would create /tags/Cpp/myProject2, in this example

No, assuming you want to name the tag "foo", it would be

/tags/foo/Cpp/myProject2

                 Your naming of directories myProject1 and myProject2 suggests that you
may have more than one project in this repository.
Yes. Is that abnormal? It would seem cumbersome to have one repository for
each project (ie application). I have about 50 applications.

No, it's fairly normal.

                 But I don't understand your organization very well. Could you have
Java/myProject2 and Cpp/myProject1, or does that not make sense to you?
Yes, theoretically that could happen. Having Java/myProject1 and
Cpp/myProject1 would mean I would have the same application written in Java
and C++

I'd recommend that you rearrange your directory layout, but that may well
not be feasible for you. The layout I'd use would be something like

myProject1/trunk/...
myProject1/tags/foo/...
myProject2/trunk/...
myProject2/tags/foo/...

where the "..." represents *everything* you would need to check out for one
copy of your project.

You could use

/trunk/myProject1/...
/trunk/myProject2/...
/tags/myProject1/foo/...
/tags/myProject2/foo/...

or just about any other permutation of the names; you should think about
what seems natural to you. And try to keep the ... all in one directory,
because it's easier to check out one subdirectory than several.

Duncan Murdoch

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jun 21 00:52:12 2006