From: news [mailto:news_at_ger.gmane.org] On Behalf Of Harry Putnam
>
> I've been a long time cvs user... but my usage has always been
> personal... no big shared projects or such.
>
> I'm starting to setup subversion and reading about common layouts in
> the docs.. I wonder how to get a little shorter path.
>
> Example... according to the docs:
>
> repo/
> myproj/
> trunk/
> project_files/
> branches/
> tags/
>
> So the working files are already 3 layers deep. That's a fair bit of
> path just to get started.
>
> I wondered what people do to get around that or do you all just live
> with it?
>
> Maybe ..symlinks? or some completely different layout from the start?
>
> A few examples from working repos of your layouts would be greatly
> appreciated here.
>
I've been using svn for about 2 years now. I came from CVS and
ClearCase. We follow this layout to the letter. You don't end up
entering these pathnames very often...once you've created a workspace,
it just remembers it for you. Unless you're doing merges and since I do
most of the merging here, I have some environment vars to make my life
easier, such as B=svn://svn/zcode/branches.
One good reason to stick with this is all the examples on tigris and
collabnet seem to follow it.
I would add one thing that's not clear in the doc. If you are trying to
decide if two subsets of your code should both be under the same project
or not, think about when you might branch and/or merge them. If they
will never branch and merge at the same time, then they should probably
be two separate projects. But if they have interdependencies, then they
almost certainly should be one project
JLM
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2404577
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-10-07 18:26:24 CEST