kfogel@collab.net wrote:
>Josh Pieper <jjp@pobox.com> writes:
>
>
>>After considering the feedback, I think a workable solution would be
>>to introduce just one new type, svn_node_special, and have it be
>>stored in the repository that way as well doing away with the
>>svn:special property. The server could translate this to a
>>svn_node_file for 1.0 clients. Then, the only system specific logic
>>would not be exported directly in any API, since it would consist of
>>just the stuff necessary to create and read the special files.
>>
>>
>
>Well, why not just introduce 'svn_node_symlink', since that's the
>goal?
>
>
Because that's not really the goal. The goal is to have a type of file
node whose contents get interpreted as a sort of file-creation command.
So if the file contents are, e.g., "symlink ../..", you'd get that in
the text base, but an actual symbolic link in the working copy itself.
You only need one new node kind for all of those.
The problem is, of course, that our WC infrastructure is woefully
inadequate for that sort of thing, so any work in that direction will
necessarily be a horrible hack.
-- Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jun 30 21:52:47 2004