steven.higgan <steven.higgan <at> orcon.net.nz> writes:
>
> 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
>
I think this is an excellent proposal and would support the sitation I've asked
for comment on here:
http://thread.gmane.org/gmane.comp.version-control.subversion.user/38996
How do you go about performing this 'manually' currently? I'm thinking of
including a script at the trunk of my project that you would need to execute
after checking out a working directory which would do 'svn export's for a set of
directories for which I do not want the overhead associated with .svn dirs on.
There is no 'post checkout hook' or any other 'client-side' hook capability is
there? I'm under the impression that all hooks are server-side.
Tim
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Oct 7 04:04:43 2005