Karl Fogel wrote:
> Blair Zajac <blair_at_orcaware.com> writes:
>> Here's my current thinking on behavior and implementation.
>>
>> - Support only intra-repository file externals. This will allow the
>> svn client to effectively do a 'touch foo; svn add foo; svn switch URL
>> foo' to have a external in the wc (those actual commands only work in
>> a 1.5 client). So unlike a directory external, the .svn/entries file
>> has entries for file externals. This is needed for supporting all the
>> client commands on a file. I don't see modifying the existing
>> directory behavior.
>
> Before implementing this, it might be good to find out how often people
> use intra-repository externals at all. My guess (uneducated, anecdotal,
> etc) is: not much. Certainly most of the externals I set are coming
> from other repositories...
>
> -Karl
Couple of my own use cases (both inter and intra repo):
1) Pull in specific jar files from normalized distro packages
2) Pull in single configuration files
3) Pull in single JSP files from common utility JSP collections
4) Subversion controlled build.number files for Ant builds
5) Pull in specific license files from common store of all licenses
6) Pull in single packagelist file for offline javadoc compilation
-The Wabbit
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-04-27 15:53:58 CEST