* [sup-talk] sup and ruby 1.9 @ 2010-10-25 23:06 Hamish D 2010-10-26 6:06 ` Michael Stapelberg 2010-10-26 10:04 ` Philipp Überbacher 0 siblings, 2 replies; 4+ messages in thread From: Hamish D @ 2010-10-25 23:06 UTC (permalink / raw) To: sup-talk Hello all I'm wondering what the status of sup and ruby 1.9 is. Is it stable and no more buggy than on ruby 1.8? Is it significantly faster than on ruby 1.8? If I did go for the change, can I switch back and forth between ruby versions? Should I reinstall all the gems that sup depends on? Thanks in advance Hamish _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [sup-talk] sup and ruby 1.9 2010-10-25 23:06 [sup-talk] sup and ruby 1.9 Hamish D @ 2010-10-26 6:06 ` Michael Stapelberg 2010-10-26 10:04 ` Philipp Überbacher 1 sibling, 0 replies; 4+ messages in thread From: Michael Stapelberg @ 2010-10-26 6:06 UTC (permalink / raw) To: sup-talk Hi Hamish, Excerpts from Hamish D's message of 2010-10-26 01:06:51 +0200: > I'm wondering what the status of sup and ruby 1.9 is. Is it stable and > no more buggy than on ruby 1.8? Is it significantly faster than on > ruby 1.8? It works just fine. I run it since a few months without any problems. For ruby 1.9.2, you need some patches: http://rubyforge.org/pipermail/sup-talk/2010-September/004223.html > If I did go for the change, can I switch back and forth between ruby > versions? Should I reinstall all the gems that sup depends on? Yes, you need to install all gems. Best regards, Michael _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [sup-talk] sup and ruby 1.9 2010-10-25 23:06 [sup-talk] sup and ruby 1.9 Hamish D 2010-10-26 6:06 ` Michael Stapelberg @ 2010-10-26 10:04 ` Philipp Überbacher 2010-10-26 10:45 ` Moritz Wilhelmy 1 sibling, 1 reply; 4+ messages in thread From: Philipp Überbacher @ 2010-10-26 10:04 UTC (permalink / raw) To: sup-talk Excerpts from Hamish D's message of 2010-10-26 01:06:51 +0200: > Hello all > > I'm wondering what the status of sup and ruby 1.9 is. Is it stable and > no more buggy than on ruby 1.8? Is it significantly faster than on > ruby 1.8? > > If I did go for the change, can I switch back and forth between ruby > versions? Should I reinstall all the gems that sup depends on? > > Thanks in advance > Hamish All I can tell you is that sup 0.11 works with ruby 1.9.1_p429 but breaks with 1.9.2. _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [sup-talk] sup and ruby 1.9 2010-10-26 10:04 ` Philipp Überbacher @ 2010-10-26 10:45 ` Moritz Wilhelmy 0 siblings, 0 replies; 4+ messages in thread From: Moritz Wilhelmy @ 2010-10-26 10:45 UTC (permalink / raw) To: sup-talk > Excerpts from Hamish D's message of 2010-10-26 01:06:51 +0200: > > I'm wondering what the status of sup and ruby 1.9 is. Is it stable and > > no more buggy than on ruby 1.8? Is it significantly faster than on > > ruby 1.8? I myself have 1.8 installed in /opt and use it for running sup. My distro (arch) likes upgrading to beta-versions way too much, and I want my mailclient to be stable ;) _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2010-10-26 11:23 UTC | newest] Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2010-10-25 23:06 [sup-talk] sup and ruby 1.9 Hamish D 2010-10-26 6:06 ` Michael Stapelberg 2010-10-26 10:04 ` Philipp Überbacher 2010-10-26 10:45 ` Moritz Wilhelmy
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox