You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by "Robert J. Gebis" <rj...@gmail.com> on 2011/10/25 20:18:33 UTC
Best project layout and branching
I switched over the weekend to 1.7.1 and read release documentation.
What I was looking was not there. Perhaps future release? What I was looking for is a "folder shadow" future found in pvsc (I used it a while back so not sure if it is it or some other tool)
I have huge project that various project depend on each other (exe and Libs on other Libs etc. Around 90 projects)
This is all setup so I can build on Windows, Mac, Solaris and Linux.
Right now I have on top level
./current
|
- 3rdPartyLib
|
|- Library1
|- Library2
|- Library3
- Library
|
|- Library1
|- Library2
|- Library3
|- Servers
|- Server1
|- Server2
./branch
|- Br1
./tag
|- Rel 1
|- …...
|- Rel 2
|
|- 3rdPartyLib
| |
| |- Library1
| |- Library2
| |- Library3
|- Library
| |
| |- Library1
| |- Library2
| |- Library3
|- Servers
|- Server1
|- Server2
to create branch I have to branch everything since all projects have relative path setup so going from current to ./branch is not possible.
What I would love to see is a "shadow" specific folder with branch. This way I could have only ./current. I think pvsc had a profile file that needed to be setup from top bottom order and folders were shadowed with appropriate branch , current or whatever.
Do you think this would be possible in the future? Is something like that on svn roadmap?
With current scenario do you have suggestions about better setup/arrangement?
Thank you
Re: Best project layout and branching
Posted by Ulrich Eckhardt <ul...@dominolaser.com>.
Am 25.10.2011 20:18, schrieb Robert J. Gebis:
> What I was looking for is a "folder shadow" future found in pvsc (I
> used it a while back so not sure if it is it or some other tool)
>
> I have huge project that various project depend on each other (exe
> and Libs on other Libs etc. Around 90 projects) This is all setup so
> I can build on Windows, Mac, Solaris and Linux.
[...]
> to create branch I have to branch everything since all projects have
> relative path setup so going from current to ./branch is not
> possible. What I would love to see is a "shadow" specific folder with
> branch.
Apart from the already mentioned svn:externals, you can also use "svn
switch .." to redirect parts of a working copy to a different URL. The
difference between the two is that switching is local to your WC while
externals are versioned. Lastly, if it's just that you are afraid of the
loads of storage a whole copy will consume in the repository, that just
isn't so. SVN optimizes copying by referring to already existing data,
so the data is not replicated.
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: Best project layout and branching
Posted by "Cooke, Mark" <ma...@siemens.com>.
> -----Original Message-----
> From: Robert J. Gebis [mailto:rjgebis@gmail.com]
> Sent: 25 October 2011 19:19
> To: users@subversion.apache.org
> Subject: Best project layout and branching
>
> I switched over the weekend to 1.7.1 and read release documentation.
> What I was looking was not there. Perhaps future release?
> What I was looking for is a "folder shadow" future found in
> pvsc (I used it a while back so not sure if it is it or some
> other tool)
>
> I have huge project that various project depend on each other
> (exe and Libs on other Libs etc. Around 90 projects)
> This is all setup so I can build on Windows, Mac, Solaris and Linux.
>
> Right now I have on top level
>
> ./current
> |
> - 3rdPartyLib
> |
> |- Library1
> |- Library2
> |- Library3
> - Library
> |
> |- Library1
> |- Library2
> |- Library3
> |- Servers
> |- Server1
> |- Server2
> ./branch
> |- Br1
> ./tag
> |- Rel 1
> |- ......
> |- Rel 2
> |
> |- 3rdPartyLib
> | |
> | |- Library1
> | |- Library2
> | |- Library3
> |- Library
> | |
> | |- Library1
> | |- Library2
> | |- Library3
> |- Servers
> |- Server1
> |- Server2
>
> to create branch I have to branch everything since all
> projects have relative path setup so going from current to
> ./branch is not possible.
> What I would love to see is a "shadow" specific folder with
> branch. This way I could have only ./current. I think pvsc
> had a profile file that needed to be setup from top bottom
> order and folders were shadowed with appropriate branch ,
> current or whatever.
>
> Do you think this would be possible in the future? Is
> something like that on svn roadmap?
>
> With current scenario do you have suggestions about better
> setup/arrangement?
>
> Thank you
It sounds like you want to read about "externals" here:-
http://svnbook.red-bean.com/nightly/en/svn.advanced.externals.html
~ mark c