"Lightweight" externals - is it possible?

 I'm developing library and sample application, which uses it. Application
and library should be released in different packages and they are different
(but coupled) projects.
 I have two projects in one repo:

app
  trunk
    ...
  tags
    ...
lib
  trunk
    ...
  tags
    ...

 But my framework (XULRunner) requires, that whole application must live in
one tree, so library tree must be injected into application one. I'm doing
this with `svn:externals', and it works. But here are two inconveniences:

(1) "svn up", "svn status" run sub-connections for externals. On link with
big latencity and "svn+ssh" used as protocol it is not very fast operation.
It is needed in general case, but in my case externasl point into same repo.
(2) "svn ci" doesn't follow externals. So, If I change application (add new
code) and change library (fix bug, which was found by this new applictaion's
code), I need two "svn ci", or even more than two, because different parts
of library (code, language files, etc) is injected in different points in
application tree.

 Is it possible to avoid these problems?

-- 
// Lev Serebryakov
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org