Branko ??ibej wrote:
> Josh Pieper wrote:
> >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.
> >
> >
> Seems reasonable. It would also be nice if the change to
> svn_subst_copy_and_translate were a bit more generic. That is, instead
> of adding another boolean flag, you could pass in the node type, or
> maybe combine the various bools into a bit mask. Both would leave room
> for future extensions.
Hmmmm, after some more investigation, it appears storing the
svn_node_special types in the repository may be challenging for any
svn before 2.0. The reason being the editor interface has no way to
specify the type of a node. It is obvious that the calling signatures
of the editor interface functions cannot be changed in a 1.x line, but
can new functions be added?
-Josh
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jun 30 14:18:23 2004