Subversion multi-Project Repository: how to?

[Pietro Moras <st...@hotmail.com>]

Very well, 
   now I dare ask the same question not in point of principle, but with a practical, operative purpose. IF multi-project Repository is really possible, HOW can be it done, in practice? 
I mean: 
1]  Is it done through the creation of a sub-Repository, at Server level, care of “svnadmin.exe”? How? Using what command?

2]  Is it done through a special creation of a single Project, at Client level, care of “svn.exe” [or, if that IDE case, some Eric VC command]? Through which command, exactly?

3]  Is there a way to select the desired Project, exclusively, both for up-loading and down-loading data, without being bothered by the possible presence of other similar and distinct Projects, within the same Repository? How, exactly? With which “svn.exe” [or, if that IDE case, some Eric VC] commands?
 It might be my fault, but what I've seen so far about this matter spans from utterly impractical to impossible, hence my stated questions. Gratefully, yours
 - P.M. 		 	   		  

Re: Subversion multi-Project Repository: how to?

[Ulrich Eckhardt <ul...@dominolaser.com>]

Am 02.03.2012 12:23, schrieb Pietro Moras:
> Very well, now I dare ask the same question not in point of
> principle, but with a practical, operative purpose. IF multi-project
> Repository is really possible, HOW can be it done, in practice?

Subversion doesn't define the term "project". This term can have lots of 
different meanings, depending on the context. Subversion provides 
versioned storage of file trees plus a few additional small features, 
but that is all.



 > 1]  Is it done through the creation of a sub-Repository, at
 > Server level, care of “svnadmin.exe”? How? Using what command?

There are no nested repositories, every repository is its own universe 
without any dependencies on other repos. What you mean is directories 
inside a repository perhaps.


> 3]  Is there a way to select the desired Project, exclusively, both
> for up-loading and down-loading data, without being bothered by the
> possible presence of other similar and distinct Projects, within the
> same Repository?

You can create a working copy (make sure you understand this term!) 
which only contains a subset of the repository it is associated with. 
This is the usual case, btw.


I think what you need to look at is the documentation explaining the 
idea behind the customary trunk/branches/tags layout. There you will 
also find a suggestion where to place that what is often considered as a 
project in this hierarchy. Also, make sure you understand both the scope 
(i.e. that SVN doesn't know what you consider a project) and 
terminology. Otherwise it's a bit difficult to communicate, if two 
people attach different meanings to the same term.


Cheers!

Uli

**************************************************************************************
Domino Laser GmbH, Fangdieckstraße 75a, 22547 Hamburg, Deutschland
Geschäftsführer: Thorsten Föcking, Amtsgericht Hamburg HR B62 932
**************************************************************************************
Visit our website at http://www.dominolaser.com
**************************************************************************************
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. Domino Laser GmbH ist für diese Folgen nicht verantwortlich.
**************************************************************************************

Re: Subversion multi-Project Repository: how to?

[Pietro Moras <st...@hotmail.com>]

>
 Subversion doesn't define the term "project". 

  And
that's it! Thank you, Uli.


  You
see [see also my former post: “Subversion
Repository: naturally a single- or multi-Project versioning
storage?”], I'm currently engaged with a project of Test &
Documentation of the “versioning” feature (i.e. Subversion)
integrated into the Eric (4) Python IDE, and I'm facing the fact
that, while Eric has a very well defined Project concept, Subversion,
clearly, hasn't. 

As
simple as that.
Thank
you again for you clarifying and convincing consideration.
All
the best. Yours, -
P.M.