Re: Repository construction

On Friday 07 March 2008, wimpunk wrote:
> 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

I would have to do some guessing in order to understand what each element is
supposed to represent. So, in order to discuss this in any way, your
colleague should first establish a (written!) description how he wants to use
this and how his setup would handle things like version numbers, tags,
releases, (feature-)branches etc.

> 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.

What is a 'major'? What is a 'project'? What is a 'module'? Any discussion
without first defining these terms is pointless.

> 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?

Yes.

> 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}

Not really. Server-side copies are cheap, regardless of the layout of the
repository.

Uli

-- 
ML: http://subversion.tigris.org/mailing-list-guidelines.html
FAQ: http://subversion.tigris.org/faq.html
Docs: http://svnbook.red-bean.com/
Sator Laser GmbH
Geschäftsführer: Michael Wöhrmann, Amtsgericht Hamburg HR B62 932
**************************************************************************************
           Visit our website at <http://www.satorlaser.de/>
**************************************************************************************
Diese E-Mail einschließlich sämtlicher Anhänge ist nur für den Adressaten bestimmt und kann vertrauliche Informationen enthalten. Bitte benachrichtigen Sie den Absender umgehend, falls Sie nicht der beabsichtigte Empfänger sein sollten. Die E-Mail ist in diesem Fall zu löschen und darf weder gelesen, weitergeleitet, veröffentlicht oder anderweitig benutzt werden.
E-Mails können durch Dritte gelesen werden und Viren sowie nichtautorisierte Änderungen enthalten. Sator Laser GmbH ist für diese Folgen nicht verantwortlich.
**************************************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org