You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Jon Cosby <jo...@jcosby.com> on 2005/06/25 18:51:21 UTC
Path structure
I've read the manual, but I just don't see the purpose of the path
structure ("tags", "trunk"). It's causing problems in one of my projects.
Would somebody explain this?
Jon
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Path structure
Posted by Russ Brown <pi...@gmail.com>.
Marc Sherman wrote:
> Russ Brown wrote:
>
>>
>> The directory structure is entirely up to you. However, if you are
>> going to want to create branches for your project, then you're going
>> to need somewhere to put them. Hence the 'branches' directory.
>
>
> Has anyone ever considered putting trunk under branches? Logically,
> trunk is a branch, and that gives the benefit that all the branches are
> at the same level, so tools can automate on [repo]/branches/([^/]+)/ .
>
That's another option, though personally I do prefer to have the trunk
stored in such a way that it is obviously separate from the other
branches. You also need to consider that you might want a hieracrical
categorisation strategy for your branches, so you can categorise them,
for example:
branches/enhancements/
branches/fixes/
branches/experiments/
etc.
That's the beauty of it: you really can arrange things any way you want.
:-)
--
Russ.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Path structure
Posted by Marc Sherman <ms...@projectile.ca>.
Russ Brown wrote:
>
> The directory structure is entirely up to you. However, if you are
> going to want to create branches for your project, then you're going
> to need somewhere to put them. Hence the 'branches' directory.
Has anyone ever considered putting trunk under branches? Logically,
trunk is a branch, and that gives the benefit that all the branches are
at the same level, so tools can automate on [repo]/branches/([^/]+)/ .
- Marc
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Path structure
Posted by Russ Brown <pi...@gmail.com>.
Adrian Hoe wrote:
> I have the same thought of Jon Cosby. Why do we need "trunk" and "branches"?
>
> Instead of
>
> project/
> calc/
> trunk/
> tags/
> branches/
>
> why not using this
>
> project/
> calc/
>
> Unless you have some slightly different set of specifications
> (requirements), otherwise, I don't see the necessity to use the former.
> I'm using the later and that's sufficient.
>
> But I don't see any problem using both.
>
> My 0.02. Cheers.
>
The directory structure is entirely up to you. However, if you are going
to want to create branches for your project, then you're going to need
somewhere to put them. Hence the 'branches' directory.
For example, where I work we currently don't bother with a tags
directory, because we don't need them, but we do have a releases
directory, which in our case is like a branch but serves a different
purpose.
The Subversion Book shows that payout because it's flexible and provides
the features available in CVS.
You can choose your on path... ;-)
--
Russ.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Path structure
Posted by Miha Vitorovic <mv...@nil.si>.
Adrian Hoe <ma...@adrianhoe.com> wrote on 26.06.2005 02:29:29:
> I have the same thought of Jon Cosby. Why do we need "trunk" and
"branches"?
>
> Instead of
>
> project/
> calc/
> trunk/
> tags/
> branches/
>
> why not using this
>
> project/
> calc/
>
I personally don't have any need for branches, but find tags very usefull.
Cheers,
---
Miha Vitorovic
Inženir v tehničnem področju
Customer Support Engineer
NIL Data Communications, Tivolska cesta 48, 1000 Ljubljana, Slovenia
Phone +386 1 4746 500 Fax +386 1 4746 501 http://www.NIL.si
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Path structure
Posted by Adrian Hoe <ma...@adrianhoe.com>.
On Jun 26, 2005, at 4:18 AM, Erik Huelsmann wrote:
>
>
>> I am asking for an explanation of the path structure.
>>
>
> Have you read
> http://svnbook.red-bean.com/en/1.1/ch05s04.html#svn-ch-5-sect-6.1 ?
>
> If it doesn't answer your questions, then:
>
> - What's unclear?
> - Where does it stop to meet your needs?
> - Why does it stop to meet your needs there?
>
> IOW: be more specific...
>
> I can't answer your question without more background.
>
> bye,
>
>
> Erik.
>
>
>
>>
>> Jon
>>
>>
>>> On 6/25/05, Jon Cosby <jo...@jcosby.com> wrote:
>>>
>>>> I've read the manual, but I just don't see the purpose of the path
>>>> structure ("tags", "trunk"). It's causing problems in one of my
>>>> projects.
>>>> Would somebody explain this?
>>>>
>>>
>>> What problems?
I have the same thought of Jon Cosby. Why do we need "trunk" and
"branches"?
Instead of
project/
calc/
trunk/
tags/
branches/
why not using this
project/
calc/
Unless you have some slightly different set of specifications
(requirements), otherwise, I don't see the necessity to use the
former. I'm using the later and that's sufficient.
But I don't see any problem using both.
My 0.02. Cheers.
--
"If you missed the rising sun and the morning dew, don't miss the
beautiful sunset." -- Adrian Hoe inspired by Michal Nowak, June 15 2004
http://adrianhoe.com
Re: Path structure
Posted by Erik Huelsmann <e....@gmx.net>.
> I am asking for an explanation of the path structure.
Have you read
http://svnbook.red-bean.com/en/1.1/ch05s04.html#svn-ch-5-sect-6.1 ?
If it doesn't answer your questions, then:
- What's unclear?
- Where does it stop to meet your needs?
- Why does it stop to meet your needs there?
IOW: be more specific...
I can't answer your question without more background.
bye,
Erik.
>
> Jon
>
> > On 6/25/05, Jon Cosby <jo...@jcosby.com> wrote:
> >> I've read the manual, but I just don't see the purpose of the path
> >> structure ("tags", "trunk"). It's causing problems in one of my
> >> projects.
> >> Would somebody explain this?
> >
> > What problems?
> >
> > (http://www.catb.org/~esr/faqs/smart-questions.html#beprecise)
> >
> > bye,
> >
> >
> > Erik.
> >
> > ---------------------------------------------------------------------
> > 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
>
--
Weitersagen: GMX DSL-Flatrates mit Tempo-Garantie!
Ab 4,99 Euro/Monat: http://www.gmx.net/de/go/dsl
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Path structure
Posted by Ben Collins-Sussman <su...@collab.net>.
On Jun 25, 2005, at 3:02 PM, Jon Cosby wrote:
> I am asking for an explanation of the path structure.
>
The explanation is: if you plan to create branches or tags of your
project, then they must exist as directories in the repository, and
thus must live somewhere.
You can use the recommended /trunk, /branches, /tags, structure if
you want, or you can make up some other set of locations to store
branches and tags. Or, if you never plan to create a branch or tag,
then you can ignore the question of layout altogether. Nobody's
forcing you to do anything here.
Chapter 4 is a long tutorial explaining branching and tagging, and
shows the "recommended" structure in action.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Path structure
Posted by Jon Cosby <jo...@jcosby.com>.
I am asking for an explanation of the path structure.
Jon
> On 6/25/05, Jon Cosby <jo...@jcosby.com> wrote:
>> I've read the manual, but I just don't see the purpose of the path
>> structure ("tags", "trunk"). It's causing problems in one of my
>> projects.
>> Would somebody explain this?
>
> What problems?
>
> (http://www.catb.org/~esr/faqs/smart-questions.html#beprecise)
>
> bye,
>
>
> Erik.
>
> ---------------------------------------------------------------------
> 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
Re: Path structure
Posted by Erik Huelsmann <eh...@gmail.com>.
On 6/25/05, Jon Cosby <jo...@jcosby.com> wrote:
> I've read the manual, but I just don't see the purpose of the path
> structure ("tags", "trunk"). It's causing problems in one of my projects.
> Would somebody explain this?
What problems?
(http://www.catb.org/~esr/faqs/smart-questions.html#beprecise)
bye,
Erik.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org