<div><blockquote class="gmail_quote" style="margin:0;margin-left:0.8ex;border-left:1px #ccc solid;padding-left:1ex">><br>>> Does SVN handle this differently?<br>><br>> yes and now.<br>> yes: you don't _have_ to create a tag and a branch whenever you
<br>> import code.<br>> no: you can import code that is maintained elsewhere into a branch,<br>> a tag, the trunk (or just any other directory)<br>> yes: svn is able to handle references to external (svn!)<br>
> repositories (which imo is better than blindly importing anything<br>> useful)<br><br>That sounds horrendous to me, then you are forced to track their<br>changes. Could you imagine if we tracked portaudio like that with
<br>Pd? We'd spent half our dev time fixing breakage caused by portaudio<br>changes. It's a very useful thing to keep code static until you are<br>ready for change.</blockquote><div><br class="webkit-block-placeholder">
</div><div>You can set a specific revision to reference, so that this does not happen.</div><div><br class="webkit-block-placeholder"></div><div>A cool thing I've been doing recently with the externals feature is using them more like symlinks; so for portaudio you can put the revision you want to stay static in a central location (
e.g. /svnexternals/portaudio) and then set /that/ as the external directory. That way you still have a single copy, but it is replicated to everywhere it is needed.</div><br> </div><div>Cheers</div><div>Luke</div>