[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Error: Working copy locked when using externals

From: Robin Guest <robin.guest_at_gmail.com>
Date: Thu, 23 Oct 2008 20:38:29 +0100

2008/10/23 Stefan Küng <tortoisesvn_at_gmail.com>

> You have a versioned folder named c:\test\bin, but you also have an
> external folder c:\test\bin. That's not possible, that's why you get
> that error.
> You have to put your externals in a subfolder of a versioned folder.

Thanks Stefan, I wondered as much. But I'm struggling to get my head round
it. Is it just that I've set up my externals wrong, or is my directory
structiure fundamentally compatible with externals?

Because it's not just c:\test\bin, c:\test\bin\Bespoke is also both a
version and an external folder. And this folder simply HAS to contain files
from both the versioned and the external project, otherwise the development
will not function when it is deployed. The projects are effectively plugins
which are loaded by the app from files in the Bespoke folder. If these files
are in a subfolder the plugins simply won't get loaded!

Having a common project which is always at the latest version without having
to manually merge revisions static copies belonging to hundreds of separate
projects, every time each is updated is my team's development policy, and
has been for 10.5 years (in SourceSafe up until now). And I cannot think of
any way of doing this in subversion without unrevisioned (HEAD) externals.

So when you say "You have to put your externals in a subfolder of a
versioned folder", how do I do this without having to move the common files
into subfolders instead of where they belong?

Please forgive me, I'm not trying to be awkward but at the moment I just
don't get it.

Cheers, Robin
Received on 2008-10-23 21:38:40 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.