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