<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Fabian ;-) -<div><br><div><div><blockquote type="cite"><div>I maintain a (acually a few) local installations of LK. It's a real<br>pain to keep these in sync with Webwerkstatt if you want to avoid a<br>complete checkout of webwerkstatt. You could check out /lively/,<br>/lib/, .. as separate modules, but not single files.<br></div></blockquote><div><br></div><div>Looking at what your problem seems to be and "asking Google", there are two very nice solutions I could find:</div><div><br></div><div>1) SVN Sparse Directories (<a href="http://svnbook.red-bean.com/en/1.5/svn-book.html#svn.advanced.sparsedirs">http://svnbook.red-bean.com/en/1.5/svn-book.html#svn.advanced.sparsedirs</a>)</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>To reproduce what is inside the "core" directory right now do:</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>svn checkout <a href="http://www.lively-kernel.org/repository/webwerkstatt2011">http://www.lively-kernel.org/repository/webwerkstatt2011</a> webwerkstatt-core --depth empty</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>cd webwerkstatt-core</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>svn update --depth infinity PartsBin Tests apps cop lib lively media ometa server users blank.xhtml webwerkstatt.xhtml</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Now you can work on things without checking everything out and being free to do "svn up" to get the latest core changes!</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>SVN will be smart enough to remember your depth settings for every directory.</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Note: I have used webwerkstatt2011 only to have the old folder structure ;o).</div><div><br></div><div>2) SVN External Definitions</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>I created a "virtual" tag using those external definitions that fetch externals from WebWerkstatt core:</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span><a href="http://www.lively-kernel.org/repository/lively-kernel/tags/current-LK2/">http://www.lively-kernel.org/repository/lively-kernel/tags/current-LK2/</a></div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>You can see the configuration after checking it out and by doing an "svn propget svn:externals".</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Because it is non-revisioned and virtual it will include all commits to the WebWerkstatt core files.</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Using this feature we can also have a "stable-LK2" with hand-selected revisions that make the stable version (changeable over time).</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Note: You will not see anything browsing to this directory (as mod_dav_svn does not show externals). You have to check it out!</div><br><blockquote type="cite"><div>On the long term, however, I think it's a good idea to have a VCS that<br>allows us to do atomic commits, especially with a growing user base.<br>To me, this is second (besides not being distributed) major drawback<br>of mod_dav_svn with autoversioning.<br></div></blockquote><div><br></div><div>I have heard that there is something better coming... (soon) ;-)</div></div><br></div></div><div>Cheers,</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>- Marko</div></body></html>