On Thu, Feb 23, 2006 at 03:07:07PM +0100, Alex Riesen wrote: >On 2/23/06, Andreas Ericsson <ae@xxxxxx> wrote: >>>>Not to be unhelpful or anything, but activestate perl seems to be quite >>>>a lot of bother. Is it worth supporting it? >>> >>> >>>It's not activestate perl actually. It's only one platform it also >>>_has_ to support. Is it worth supporting Windows? >> >>With or without cygwin? With cygwin, I'd say "yes, unless it makes >>things terribly difficult to maintain and so long as we don't take >>performance hits on unices". Without cygwin, I'd say "What? It runs >>on windows?". > >There not much difference with or without cygwin. The penalties of >doing any kind of support for it will pile up (as they started to do >with pipes). Someday we'll have to start dropping features on Windows >or restrict them beyond their usefullness. The fork emulation in >cygwin isn't perfect, If the speed of cygwin's fork is an issue then I'd previously suggested using spawn*. The spawn family of functions were designed to emulate Windows functions of the same name. They start a new process without the requirement of forking. >signals do not work reliably (if at all), I'm not sure if you're mixing cygwin with windows here but if signals do not work reliably in Cygwin then that is something that we'd like to know about. Signals *obviously* have to work fairly well for programs like ssh, bash, and X to work, however. Native Windows, OTOH, hardly has any signals at all and deals with signals in a way that is only vaguely like linux. >filesystem is slow and locked down, and exec-attribute is NOT really >useful even on NTFS (it is somehow related to execute permission and >open files. I still cannot figure out how exactly are they related). Again, it's not clear if you're talking about Windows or Cygwin but under Cygwin, in the default configuration, the exec attribute means the same thing to cygwin as it does to linux. As always, if you have questions or problems with cygwin, you can ask in the proper forum. The available cygwin mailing lists are here: http://cygwin.com/lists.html. Would getting git into the cygwin distribution solve any problems with git adoption on Windows? This would get an automatic green light from anyone who was interested, if so. Someone would just have to send an "ITP" (Intent To Package) to the cygwin-apps mailing list and provide a package using the guidelines here: http://cygwin.com/setup.html . cgf -- Christopher Faylor spammer? -> aaaspam@xxxxxxxxxxxxxx Cygwin Co-Project Leader TimeSys, Inc. - : send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html