RE: [RFC] Ability to add external directories as exported paths

I do this exact thing, albeit manually

How I see this working is as follows

trunk
 - /proj/
 - /proj/aLib/ svn:exports http:\\server\repo\thirdParty\thisLibary

When trunk/proj is checked out the contents of proj/ will be checked out as
per normal but the directory /aLib/ will export the contents of the
repo-path located in the property.

The admin files inside the proj wc should say that 'proj/aLib' is an
'exported' directory so that when a commit is ran on 'proj/ it would ignore
anything inside that 'exported' directory and its children.

Of course all of the other wc commands will need to know about this
'exported' property and how to deal with it.

As for putting a 'svn:ignore' on it, yes you could do that but you would
loose the ability for wc commands to operate on the exported directory
(updating, ls, are two examples)

How does everybody else feel

-----------------------------------------------
Steven H, 3rd Year B.I.T. Dunedin, New Zealand
.net madGeek
 

-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.344 / Virus Database: 267.11.10/120 - Release Date: 5/10/2005
 
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org