Ben Reser <ben@reser.org> writes:
> I'd love to see this fixed rather than hacked around. I said something
> about this shortly after 0.35.0 IIRC. There seems to be little interest
> in fixing it from the core end. The only solution seems to be changes
> to the build system which I don't understand well enough to do anything
> to. So I can't just submit a patch to fix it. Not without a lot more
> time than someone else who already understands the build system. So it
> seems a lot more effective use of my time to work on the stuff I do
> understand, use a workaround for now, and let someone else fix the build
> system. If you consider that a poor attitude I'm sorry you feel that
> way. It's not like I didn't raise the issue to you guys.
Oh, I don't think Greg (or anyone) was accusing you of poor attitude,
don't worry. He's just describing a state of affairs.
One useful thing would be: if you feel there's a Right Way to fix
something, but you only had the time or domain knowledge to contribute
a workaround, then after the workaround is committed you can file an
issue describing the more desirable fix. At least then we could keep
track of this stuff, and have a reference point for someone who does
have the time/skills to solve the problem.
-K
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jan 8 20:22:04 2004