Dirk wrote:
I started a new module AutoProps to start development on this issue. I
is currently only a simple module that will read a subversion config.
But there is no functionality in there. Only a test. We will get a
hash of filepatterns/properties. So the next step is to evaluate the
itempath against all filepatterns and to add all properties if the
filepattern matches.
Discussion:
* if mulitple patterns match, all properties of all matching patterns
should be added
* per file pattern multiple properties can be specified, seperated by
semicolon
* What should happen if the same property is added twice
* with the same value
* with a different value
I'm pretty sure I've read at one point in the Subversion docs that
adding the same property multiple times causes an indeterminate result,
but that the current implementation is that the "last one wins". At any
rate, that sounds like a "good enough" solution to me. So that means we
should build a hash of property => value pairs for each node.
* where to integrate?
* Dumpfile::_add_handler
* Node::Set_initial_properties
Auto-props are only used by Subversion when a file is first added, so I
think Dumpfile::_add_handler() makes sense.
* can properties change in a subversion "change" node?
I'm pretty sure they can, although it's a moot point for autoprops since
they're only used on adds.
Since I'm not the best PERL programmer I just have started the
development. Anybody out there, to pick it up from here ;-)
Thanks, it's a good start. :) I can probably knock this out when I get
some free time.
toby
_______________________________________________
vss2svn-users mailing list
Project homepage:
http://www.pumacode.org/projects/vss2svn/
Subscribe/Unsubscribe/Admin:
http://lists.pumacode.org/mailman/listinfo/vss2svn-users-lists.pumacode.org
Mailing list web interface (with searchable archives):
http://dir.gmane.org/gmane.comp.version-control.subversion.vss2svn.user
