hakon@ion.no wrote on 07/01/2006 09:40:13 AM:
> Would you care to mention the difficulties with properties? All I can
> think of is:
> 1. It is not possible to commit changes to single property on a
> file/directory.
> 2. It is not simple to search properties based on their values. Or sort
> the properties based on their values.
These are the main issues with using properties as I see them:
1) The property needs to be available in the WC to be used. If the tag
property is just on a specific folder, and you checked out some
sub-folder, then now you don't have the property available to be used.
This is why the feature works in Subclipse, because there are very
specific folders that an Eclipse user will check out. Setting the
property on every folder is unmanageable. The solution we have talked
about is something called "inherited properties", but there are some messy
issues to deal with to do that.
2) You cannot set a property directly on a URL. This is technically
feasible, it just has not been allowed or exposed. In this case, since
you'd only want to append to the existing value, maybe it would be a
capability that could be added?
3) Since properties are versioned, they require a commit. This might be
the sort of thing that could be combined with #2 so that if we had a
special svn tag command, it could under-the covers, to the copy and the
update of the tag property in a single atomic operation.
4) Once you have properties they are not easily searchable. For this
particular feature, I am not sure how significant a problem that is.
5) As others have pointed out, a single property value cannot easily
express a complex mixed-revision tag.
Thanks
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jul 1 19:52:29 2006