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

Re: Preventing a folder from being checked out?

From: Olivier Sannier <obones_at_free.fr>
Date: 2005-07-01 10:45:42 CEST

Oh but I understand all that.
The thing is that I want my tags to apply to the whole source tree, not
just to "project1" or "project2".
And I would much prefer if I could not have a "trunk" directory at the
root because it has "no real use" to me.
I will hardly do any branches, but tags will be quite frequent, and
that's why I want to keep them separate.
Isn't there any way to do this?

Jake Robb wrote:

>Olivier,
>
>I think that you are confused about the recommended best practices for
>repository layout.
>
>The basic idea is to have the root of your repository contain a directory
>for each of your projects, and have each project directory contain three
>more directories -- trunk, branches, and tags.
>
>A new developer shouldn't be doing a checkout of /. Based on your examples,
>he (or she) should be doing a checkout of /libs/, /project_one/trunk/, and
>/project_two/trunk/. This means it will take a little bit more time to do
>the initial checkout, but you'll find that it's quite easy, especially if
>you're using a nice GUI tool like TortoiseSVN (my tool of choice when I'm
>using Windows).
>
>For more details, please refer to the Subversion Book:
>http://svnbook.red-bean.com/
>
>I think you will find chapter 5, section 6.1 most helpful.
>
>-Jake
>
>-----Original Message-----
>From: Olivier Sannier [mailto:obones@free.fr]
>Sent: Thursday, June 30, 2005 4:44 PM
>To: users@subversion.tigris.org
>Subject: Preventing a folder from being checked out?
>
>Hi all,
>
>Coming from CVS, I was used to having tags and branches be a "virtual"
>concept.
>But now that I work with SVN at work, I just started to wonder about
>branches, and as it turns out, this is more "real", in the sense that
>there needs to be folder for branches. The thing is that I've already
>created the repository like this:
>
>/libs/somelib
>/libs/someotherlib
>/project_one
>/project_two
>
>This is fine with me and if I want to create tag or a branch, I actually
>have to make it on everything, the projects being heavily interdependent
>on the libs.
>So if I was to create tag, I should put it inside a "tags" branch and
>end up with this:
>
>/libs/somelib
>/libs/someotherlib
>/project_one
>/project_two
>/tags/sometag/libs/somelib
>/tags/sometag /libs/someotherlib
>/tags/sometag /project_one
>/tags/sometag /project_two
>
>But if a new developer comes in and does a checkout of /, he will get
>all the tags, which is not desirable, as he will have to work on trunk
>anyway. So I'm wondering if there is a way to say: don't include "tags"
>in a checkout made on / but let it go through if the checkout
>specifically requests it.
>Is this at all possible? If yes, how?
>I would very much prefer if I would not be forced to create a "trunk"
>folder at the root and put everything into it. The current organisation
>makes the tags and branches transparent except to those who really want
>them.
>
>Thanks for your help
>Olivier Sannier
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>For additional commands, e-mail: users-help@subversion.tigris.org
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>For additional commands, e-mail: users-help@subversion.tigris.org
>
>
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jul 1 10:48:52 2005

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