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

RE: Repository construction

From: Reedick, Andrew <jr9445_at_ATT.COM>
Date: Fri, 7 Mar 2008 11:07:32 -0600

> -----Original Message-----
> From: news [mailto:news_at_ger.gmane.org] On Behalf Of wimpunk
> Sent: Friday, March 07, 2008 11:21 AM
> To: users_at_subversion.tigris.org
> Subject: Repository construction
> Hi,
> A college has a rather strange idea on setting up his repository and
> I'm
> wondering if it will cause any troubles for subversion since I'm the
> administrator.
> He's used working with SourceSafe and now he's planning to use a
> directory structure looking like this:
> project/major/module/minor/version
> Personally I would remove major, minor and version from the structure
> but he really wants it that way. When he starts a new major, he
> creates
> the substructure again and copies the latest version to this major.

That's fine. Subversion copies are very lightweight and fast.
        svn copy svn://.../project/1.0 svn://.../project/2.0

> As far as I understand, there's no server-side objection doing this.
> For subversion is doesn't matters where you create your branch. Is
> this
> correct?
> Will it differ at the server size concerning the size of the db if we
> use a more normal construction like this:
> project/module/{trunk,branches,tags}

No real issues to worry about. However there will be some potential

- Checking out project/major will get every module and every module's
minor versions. =P You might want to let the user know about the 'svn
co -N' option to selectively checkout just what he wants to work on.

- Merging between minors should be easy
        Svn merge ... svn://.../project/1.0/module/minor/version

- but merging an entire major or module won't be
        svn merge ... svn://.../project/1.0/
  since it will merge every minor version also.

- he will need to create a branches or tags directory at some point, if
just for experimental throwaway code.
        svn copy svn://.../project/2.0

Honestly, the directory structure he uses would seem to be just as
awkward in VSS.


The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential, proprietary, and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from all computers. GA625

To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-03-07 18:08:38 CET

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.