Ulrich Eckhardt wrote on Thu, Nov 25, 2010 at 09:38:25 +0100:
> I have a scenario where I can't update a working copy while an update on an
> unrelated other working copy is in progress. The directory structure looks
> like this:
> foo-test-1 *
> foo-test-2 *
> Now, what makes this special is that in the repository, the marked foo-test
> directories don't exist. These directories are just file-system copies of foo
> which I made in order to do some tests while keeping the relation to lib_bar.
> Theoretically, they should be independent roots of separate WCs, right?
> However, while running update on either foo-test, it seems that the projects
Have you tried both 'cd projects; svn up foo-test-1' and 'cd projects/foo-test-1; svn up'?
> root dir is locked, so I can't update the rest. However, I can update both
> foo-test WCs in parallel.
> Also, I wonder how the new 1.7 WC format will affect me here. As far as I
> know, the metadata is stored in just the root folder of the working copy
> there, which means that a file-system copy of a subdir is not a working copy
> on its own, which means I can't achieve the above by using a file-system copy
> but have to do a separate checkout of the subdirectory, rigth?
> I also thought about using a local never-committed copy, which I would then
> switch back to the original dir:
> svn cp foo foo-test
> svn switch $(REPOS)/projects/foo foo-test
> This should even allow me to update all my folders by issuing an update on the
> projects root folder. Well, at least it could, I don't know if it works, I'm
> not even sure it should work.
Or just use svn:externals to pull foo-test as foo-test-1.
> ML: http://subversion.apache.org/docs/community-guide/mailing-lists.html
> FAQ: http://subversion.apache.org/faq.html
> Docs: http://svnbook.red-bean.com/
Received on 2010-11-25 11:29:04 CET