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

Re: I miss tags

From: Raye Raskin <rayer_at_pobox.com>
Date: 2004-09-29 04:01:20 CEST

----- Original Message -----
From: "Stephen Webb" <swebb@netlab.uky.edu>
To: "Subversion Users" <users@subversion.tigris.org>
Sent: Tuesday, September 28, 2004 5:42 PM
Subject: Re: I miss tags

>
>
>> Let's assume they have "trunk" checked out. Then they won't
>> get my_new_tag. If they have the entire repository checked
>> out, PARBI [1], they'll get it. Or if they have tags checked out,
>> I assumed they'd also get it.
>>
>> Raye.
>>
>> [1] PARBI - Probably A Really Bad Idea
>
> Uh oh. Why?

First of all, I thought "calc" in your example was the name of
the repository since you didn't show any parent.

Second, you wouldn't want to get the trunk and all the branches
and all the tags whenever you check out or update libs (or even
just lib1, as in your example) would you? So I guess your plan
is to check out, for example, libs/lib1/trunk calling it "lib1"
as your working directory name as you do so, eh?

Perhaps this is a philosophical choice, but I don't see why you
would want to have dozens or even hundreds of directories named
trunk, branches, and tags when you could have just one of each.

Sure, you'll need one directory for each "project" under trunk
but there's no getting around that. And you'll need one dir
for each branch or (dare I say it) tag that you create.

Still, I'm new to svn (though not to SCM) so there may be a
better svn way to do it.

There's more than one way to skin a cat...

Raye.

> Maybe I misunderstood how the repository would be used, but I didn't
> imagine people checking out just the trunk directory for a project. I
> suppose that does work, but with my structure...
>
> libs/
> lib1/
> trunk/
> branches/
> lib2/
> trunk/
> branches/
> lib3/
> trunk/
> branches/
>
> projects/
> project1/
> ...
>
> admin/
> scripts/
> usage/
> ...
>
> Everyone is likely to need all (most) of the libs. The natural thing (I
> thought) would be to have them checkout the libs directory. The
> alternative is to check out the trunk for each subdir in libs...(which
> could be time consuming). I suppose the trunk/branches/tags dir could
> live under libs...and they would just check out libs/trunk. But then why
> not put trunk/branches/tags all the way at the root?
>
> I think it's just a mental thing -- I think of the "lib1 project" living
> in libs/lib1 -- checking out only "part" of the libs/lib1 directory (ie
> just the trunk) somehow feels weird. If I think of the "lib1 project" as
> living in libs/lib1/trunk, maybe that would help.
>
> -Steve
>
>
>
> ---------------------------------------------------------------------
> 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 Wed Sep 29 04:02:08 2004

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