Hi, just wondering if there are plans to bring the version of Rubygems that is bundled with MacRuby up to date any time soon. The current version with MacRuby 0.10 is Rubygems 1.4.2 -- quite a bit behind standard Rubygems, which is at 1.8.15. This becomes a problem when certain gems are configured to only install on fairly recent versions of Rubygems... Thanks, -Gabriel
It's always quite a lot of work, especially when a new release is pushed weekly. Could you open a ticket tho? Thanks On Mon, Feb 6, 2012 at 2:21 PM, Gabriel Gilder <gabriel.gilder@gmail.com>wrote:
Hi, just wondering if there are plans to bring the version of Rubygems that is bundled with MacRuby up to date any time soon. The current version with MacRuby 0.10 is Rubygems 1.4.2 -- quite a bit behind standard Rubygems, which is at 1.8.15. This becomes a problem when certain gems are configured to only install on fairly recent versions of Rubygems...
Thanks, -Gabriel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Is the work something you could train me on? Sent from my iPhone On Feb 7, 2012, at 5:14 PM, Matt Aimonetti <mattaimonetti@gmail.com> wrote: It's always quite a lot of work, especially when a new release is pushed weekly. Could you open a ticket tho? Thanks On Mon, Feb 6, 2012 at 2:21 PM, Gabriel Gilder <gabriel.gilder@gmail.com>wrote:
Hi, just wondering if there are plans to bring the version of Rubygems that is bundled with MacRuby up to date any time soon. The current version with MacRuby 0.10 is Rubygems 1.4.2 -- quite a bit behind standard Rubygems, which is at 1.8.15. This becomes a problem when certain gems are configured to only install on fairly recent versions of Rubygems...
Thanks, -Gabriel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
I'm not sure if any specific "training" is possible. The first thing you might want to do is try to run the rubygems test suite under MacRuby, just to see if it even runs. I tried it, one test crashed, but it finished and here are the results for me: 882 tests, 2489 assertions, 34 failures, 113 errors, 0 skips Of course, that was mixed with a whole whack of warnings. However, I believe it the test suite couldn't even finish when I tried last (almost a year ago). Next you might want to find the MacRuby patches to rubygems and see if you can apply them, or if you even need them, on the current rubygems source. You can find the patches if you search the MacRuby lib/ directory for "XXX MACRUBY". If we're lucky, all the tests will pass at that point and you can try building macruby with a new rubygems to see if it actually works. If not, we would have to evaluate which things to fix; it might not be worthwhile to fix some edge cases right now. Like Matt said, it' s not a simple job... PROTIP: running the rubygems test suite under macruby seems to mess with your ~/.gemrc file and then doest fix it afterwards, whereas it would restore the original when running the tests under CRuby; now, when rubygems stops working after you run the test suite you'll know why Hope that helps, Mark On 2012-02-07, at 5:20 PM, Kevin Poorman wrote:
Is the work something you could train me on?
Sent from my iPhone
On Feb 7, 2012, at 5:14 PM, Matt Aimonetti <mattaimonetti@gmail.com> wrote:
It's always quite a lot of work, especially when a new release is pushed weekly. Could you open a ticket tho?
Thanks
On Mon, Feb 6, 2012 at 2:21 PM, Gabriel Gilder <gabriel.gilder@gmail.com> wrote: Hi, just wondering if there are plans to bring the version of Rubygems that is bundled with MacRuby up to date any time soon. The current version with MacRuby 0.10 is Rubygems 1.4.2 -- quite a bit behind standard Rubygems, which is at 1.8.15. This becomes a problem when certain gems are configured to only install on fairly recent versions of Rubygems...
Thanks, -Gabriel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Interesting, I did poke around and notice the MacRuby commented bits... anyway, I've added a ticket for now: https://www.macruby.org/trac/ticket/1450 Thanks, -Gabriel On Feb 7, 2012, at 6:40 PM, Mark Rada wrote:
I'm not sure if any specific "training" is possible. The first thing you might want to do is try to run the rubygems test suite under MacRuby, just to see if it even runs. I tried it, one test crashed, but it finished and here are the results for me:
882 tests, 2489 assertions, 34 failures, 113 errors, 0 skips
Of course, that was mixed with a whole whack of warnings. However, I believe it the test suite couldn't even finish when I tried last (almost a year ago).
Next you might want to find the MacRuby patches to rubygems and see if you can apply them, or if you even need them, on the current rubygems source. You can find the patches if you search the MacRuby lib/ directory for "XXX MACRUBY". If we're lucky, all the tests will pass at that point and you can try building macruby with a new rubygems to see if it actually works.
If not, we would have to evaluate which things to fix; it might not be worthwhile to fix some edge cases right now. Like Matt said, it' s not a simple job...
PROTIP: running the rubygems test suite under macruby seems to mess with your ~/.gemrc file and then doest fix it afterwards, whereas it would restore the original when running the tests under CRuby; now, when rubygems stops working after you run the test suite you'll know why
Hope that helps, Mark
On 2012-02-07, at 5:20 PM, Kevin Poorman wrote:
Is the work something you could train me on?
Sent from my iPhone
On Feb 7, 2012, at 5:14 PM, Matt Aimonetti <mattaimonetti@gmail.com> wrote:
It's always quite a lot of work, especially when a new release is pushed weekly. Could you open a ticket tho?
Thanks
On Mon, Feb 6, 2012 at 2:21 PM, Gabriel Gilder <gabriel.gilder@gmail.com> wrote: Hi, just wondering if there are plans to bring the version of Rubygems that is bundled with MacRuby up to date any time soon. The current version with MacRuby 0.10 is Rubygems 1.4.2 -- quite a bit behind standard Rubygems, which is at 1.8.15. This becomes a problem when certain gems are configured to only install on fairly recent versions of Rubygems...
Thanks, -Gabriel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
participants (4)
-
Gabriel Gilder
-
Kevin Poorman
-
Mark Rada
-
Matt Aimonetti