StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>Using <code>svn:externals</code> as a poor man's dependency management or code duplication avoidance scheme are the source of your woes. Nesting them is not double bad, it's multiplicative. I recommend this <a href="https://stackoverflow.com/a/345404/505191">excellent long answer about the badness with externals</a></p> <p>You're never going to have great results using <code>svn:externals</code> for internal stuff, however if you keep using them you can mitigate the pain by:</p> <ol> <li>Follow the advice of the <a href="http://svnbook.red-bean.com/en/1.7/svn.advanced.externals.html" rel="nofollow noreferrer">red book</a> and never make an external pull in the head:</li> </ol> <blockquote> <p>You should seriously consider using explicit revision numbers in all of your externals definitions. Doing so means that you get to decide when to pull down a different snapshot of external information, and exactly which snapshot to pull. Besides avoiding the surprise of getting changes to third-party repositories that you might not have any control over, using explicit revision numbers also means that as you backdate your working copy to a previous revision, your externals definitions will also revert to the way they looked in that previous revision, which in turn means that the external working copies will be updated to match the way they looked back when your repository was at that previous revision. For software projects, this could be the difference between a successful and a failed build of an older snapshot of your complex codebase.</p> </blockquote> <ol start="2"> <li>If you don't do the above, create your tags with <a href="http://svn.apache.org/repos/asf/subversion/trunk/contrib/client-side/svncopy/svncopy.pl.in" rel="nofollow noreferrer">svncopy.pl</a>. It will 'pin' the revisions of your externals to whatever they are when you create the tag.</li> </ol> <p>You didn't mention why you have multiple repositories - is it possible you may benefit from consolidation?<br> You didn't mention what language/tooling your working with. I'm pretty sure there is a better way for you to meet your requirements. For example, if it's a java app with a few librairies you're pulling in via the externals - you'll be happier if you build the libraries separately and publish them using some maven like substance and then resolve them when you build your app.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload