Matt Slot <fprefect_at_ambrosiasw.com> writes:
> The data is in a standardized and supported format, so it should be
> forward compatible. It's also "optional", in that platforms which
> don't recognize Mac resource forks won't be affected, nor will older
> subversion releases.
The sole and only issue here, as far as I can see, is the additional
complexity this would put in the Subversion core code. We'll have to
maintain it, and naturally are a little reluctant. It's not that the
patch is bad, nor the feature undesirable. It's just a question of
overall cost/benefit (yes, I understand that the benefit for Mac
developers is huge, but that's still a subset of all users).
I don't have a suggestion for how to resolve this, I just want to focus
us on what the issue is. The quality of the patch itself is not the
issue.
I do wonder if, instead of maintaining a custom patch, it might make
more sense to maintain a script that wraps svn and DTRT with such
bundled directories. I do something similar to achieve encrypted
working copies, and while it's not quite as smooth as just working with
native Subversion, it's also not very inconvenient (for me, anyway,
though of course I'm overly familiar with my version control tools,
relative to most users).
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-08-11 08:09:29 CEST