Well, we have been using that feature in production in our web-startup for over a year and a half, if it is any consolation? Why do you say it is "beta-testing"? SVN is not exactly a bleeding edge technology at this point ; ); the externals feature has been there since at least 2002 judging by the changelog.
<div><div><br class="webkit-block-placeholder"></div><div>Cheers</div><div>Luke<br><div><br><div><span class="gmail_quote">On 9/13/07, <b class="gmail_sendername">Hans-Christoph Steiner</b> <<a href="mailto:hans@eds.org">
hans@eds.org</a>> wrote:</span><blockquote class="gmail_quote" style="margin:0;margin-left:0.8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><br><div><div><span class="e" id="q_114ff806fd020fe9_1">
<div>On Sep 13, 2007, at 12:06 AM, Luke Iannini (pd) wrote:</div><br><blockquote type="cite"><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> </div><div>You can set a specific revision to reference, so that this does not happen.</div><div><br> </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></blockquote><div><br> </div></span></div>
<div>How well does this really work in production? It's really pretty easy to import code into repositories and manage it there. The idea is cool, but I am not really up for beta testing svn features. There are plenty of Pd bugs to deal with :D. This import feature has been around for 10+ years in CVS at least.
</div><div><br> </div><div>.hc</div><br><blockquote type="cite"><div> </div><div>Cheers</div><div>Luke</div></blockquote></div><br><div> <span style="border-collapse:separate;border-spacing:0px 0px;color:rgb(0, 0, 0);font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">
<br><div><br> </div><div><br> </div><div>----------------------------------------------------------------------------<br></div><div><br> </div><div> kill your television</div><br></span> </div><br>
</div><br>_______________________________________________<br>PD-dev mailing list<br><a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:PD-dev@iem.at">PD-dev@iem.at</a><br><a onclick="return top.js.OpenExtLink(window,event,this)" href="http://lists.puredata.info/listinfo/pd-dev" target="_blank">
http://lists.puredata.info</a><a onclick="return top.js.OpenExtLink(window,event,this)" href="http://lists.puredata.info/listinfo/pd-dev" target="_blank">/listinfo/pd-dev</a><br><br></blockquote></div><br> </div></div></div>