Absolutely! If you feel that you would like to leave this one out, I'm perfectly fine with that. I don't have access to a Windows machine to perform much in the way of testing there so I'm happy to defer the matter.
Cool.
(Unless maybe someone already has a *confirmed working* Cygwin build/test environment running under Wine on Ubuntu perhaps.)
My build environment ssh's to a windows box running cygwin to do the actual builds.
That being said, are you already aware of some other things that are likely to work only on your machine? These might be good candidates for me to start thinking about maybe improving/automating.
That remote script is really the only one that's super hacky I think. It's really not useful unless someone wants to setup remote win32 builds from a linux machine, and even still, it's just one way to do it. I put it in the tree mostly just in case I get hit by a bus and because the builds get generated from the tree mostly without any external help. I don't know of anyone else that runs any of this stuff other than me (not much point) so I don't think it's worth a whole lot of effort, to be honest :)
--Dan