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

Re: Repository structure (project with different sub-projects)

From: MarcoE <sperber73_at_yahoo.de>
Date: Mon, 11 Aug 2008 00:25:39 -0700 (PDT)

Thank you for your answer.
I've understood your general explanations and that is the way I've
structured the repository.
Reason for putting trunk/branch/tag into the project and not in front of the
We will have different projects and not all of them should appear in the
same tag/branch directory.

But if you have a better idea to structure it, please let me know.

If made my first tests and it seams that this solution is possible.
As far as I understood the properties will be released too?
How do you use/organize the svn:externals? During development process HEAD
and when you create an new release (tag) of your product, you change the
svn:externals and switch to the current folder revision of the released

How can you keep an overview about all your svn:externals? Is there a
graphical diagram or something else? It seams to be a problem to get
overview about the different used svn:externals properties.
Same problem for the developer who checked out the project sources. Checkout
means that the "linked" sub-project will be exported too. If somebody
changes the svn:externals properties, will an "svn update" update the local
environment too?

Best regards and thanks a lot

View this message in context: http://www.nabble.com/Repository-structure-%28project-with-different-sub-projects%29-tp18844825p18921179.html
Sent from the Subversion Users mailing list archive at Nabble.com.
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-08-11 09:26:09 CEST

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.