As a user of ruby on windows & linux & osx. I have no problem with the position your taking. Cap/Net-ssh are is a open source tools, so if the community wants something that you are not working on, then they should either fix it themselves or hire someone to do so and then contribute the fixes back to the community.
Hopefully a lot of the windows drama will go away with "production" releases of IronRuby. Until then there are enough free solutions for people on windows to run linux vms to get around the windows problems. (ie- VMWare player, coLinux/andLinux, etc...) Hell even using cygwin should work (puttycyg makes cygwin somewhat usable). On Dec 7, 9:08 am, "Jamis Buck" <[EMAIL PROTECTED]> wrote: > On Sun, Dec 7, 2008 at 9:22 AM, Larry <[EMAIL PROTECTED]> wrote: > > > I noticed that you were ditching support for Solaris because of > > similar problems. I understand that, too. But the problem is that > > there are undoubtedly a lot more Windows users than Solaris, and > > although *nix is the platform of choice for RoR enthusiasts, the > > number of Rails developers using Windows is rather large and will > > continue to grow. I am no fan of Microsoft, but, like it or not, they > > are the 800 lb. gorilla in the room. > > I'm realizing something about myself and Capistrano. I've been burning > out on cap lately, and I've been trying to figure out why. > > I wrote Capistrano for me. I didn't write it to have lots of users. I > didn't write it to be a popular solution to a problem. I wrote it to > scratch my itch. It's been a nice side-effect that so many people have > found it useful, but that wasn't my purpose. > > I'm burning out because suddenly I'm feeling an obligation to keep > everyone happy. It is a false obligation, though: I'm honestly not > beholden to anyone for Capistrano's maintenance. I've never received a > cent for my work on cap (and I don't want to receive money for > it--that would put me right back in the obligation boat, and with > better reason). > > Something has to give. In this case (and among other things), it's > Windows. Microsoft may be an 800lb gorilla, but it's not _my_ gorilla, > and it's not in _my_ room. If you need to appease the gorilla, that is > (with all due respect) not my problem. If it happens to be your > problem, please feel free to make the time to get acquainted with > Net::SSH and Capistrano, and scratch your itch. > > And, frankly, Capistrano is not _it_ when it comes to deployment. If > nothing else, you can always go back and do what everybody did > pre-capistrano: do it by hand. > > Now, if you're stuck in Windows by corporate policy, you have my > sympathy. But I'm still not budging on this issue. I will not break my > back or my sanity on Windows troubleshooting any more. > > On the other hand, if you're stuck in Windows by choice, you don't > even have my sympathy. :) It is to YOU that I'm speaking, directly, > when I say that if you want Capistrano on Windows, then it's your > responsibility to do something about it. Either you make Cap work on > Windows and send patches upstream, or you write your own solution from > the ground up. > > > Is there a previous release that we can back up to that will work with > > Windows? Or can you suggest any other alternatives? > > Any Cap 2.x release ought to work fine on windows. If the pageant > thing is biting you, disable ssh agent forwarding: > > ssh_options[:forward_agent] = false > > If that doesn't work...well, again. It's not my problem anymore. I'm > sorry to come across so callous, but it's what I have to do right now > to keep myself motivated to work on Capistrano at all. > > - Jamis --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
