On Fri, Jul 01, 2011 at 03:11:08PM +0300, Gabor Szabo wrote:
> So I'd like to ask you all to check the test reports of your modules and if
> you
> have consistent failures of one of your modules on Windows then try to fix
> them.
> If you need any help, please send a message on either of those mailing list
> asking people how to fix specific Windows related issues.
I went through a period of trying to make sure my code worked on
Windows, but I've given up. Not because it's hard to do - it generally
isn't - but the complete lack of a reasonable set of tools* on Windows,
which just makes me angry whenever I have to touch the blasted thing,
made me stop.
* starting with a useable shell and editor, documentation, and remote
text-based access. No doubt it doesn't help that I have no need for
Windows, either personally or professionally, so have no motivation
to put the effort into learning it.
I am, of course, happy to accept patches, provided that they are
adequately documented and have tests, on the understanding that I can't
run Windows tests, and may therefore accidentally break them again in
the future.
--
David Cantrell | semi-evolved ape-thing
[OS X] appeals to me as a monk, a user, a compiler-of-apps, a
sometime coder, and an easily amused primate with a penchant
for those that are pretty, colorful, and make nice noises.
-- Dan Birchall, in The Monastery
