Externals handling...

Hi!

I just played around with externals properties (there's a huge need for those
in our projects).

They worked fine on checkout, and I had a nice source tree. The problem came
later, when I began coding on the tree and committed changes. I noticed that
the 'external' directories where not recursively committed, too, as I had
expected.

Looking in the code, there seems to be no handling of this. Is this correct?
If so, why? I didn't find any mention of the intended behaviour in the book,
and no filed issue of this.

Just out of curiosity, I the added such an 'external' directory to the main
project, and the next commit handled the directory well (means changed files
were committed too, obviously to the correct repository).
Interestingly now an svn status lists this directory as 'switched', and svn
update now reports:

Fetching external item into Queue_SM_JH
svn: Attempted to lock an already-locked dir
svn: working copy locked: Queue_SM_JH
svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details)

You can't do updates again until you explicitly remove the directory from the
main project again, then re-update.

Can someone sched some light on what is the intended behaviour?
Is there an issue here?

(This was tested with 0.18.1, rev. 5118 on a PIII Debian woody box, local
repositories).

Greetings,
        Joerg

-- 
Leading SW developer  - S.E.A GmbH
Mail: joerg.hessdoerfer@sea-gmbh.com
WWW:  http://www.sea-gmbh.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org