On Aug 12, 9:15 pm, Jon Hancock <[email protected]> wrote: > trying again...doing a cleanup first.> sudo gem191 uninstall merb-core > > Remove executables: > merb > > I answer Yes, it tells me it uninstalls. So I then check: > > > which merb > > /usr/bin/merb > > > which merb191 > > /usr/local/bin/merb191 >
I'm really not sure if this is a Merb problem it's more a gems problem. If gems are able to install merb-core and create merb19 executable and later gems are not able to uninstall merb19 executable than it's gems problem. Merb doesn't do any with the executables unless you do bundling. > seriously, how bad does this get? I have heard people telling merb is > working under 1.9.1. Seems pretty broke to me so far. > > On Aug 12, 3:29 pm, Jon Hancock <[email protected]> wrote: > > > > > I've installed ruby 1.9.1-p243 on OS X. Managed to get it coexisting > > with ruby 1.8.6 as near as I can tell. > > Then installed merb gems: > > sudo gem191 install methopara --format-executable > > sudo gem191 install merb --format-executable > > > I get these errors when running merb on a barebones project which > > works under 1.8.6: > > > > merb191 -a thin > > > /usr/local/lib/ruby191/gems/1.9.1/gems/merb-core-1.0.12/lib/merb-core/ > > dispatch/router/behavior.rb:18: warning: undefining `object_id' may > > cause serious problem > > /usr/local/lib/ruby191/gems/1.9.1/gems/merb-core-1.0.12/lib/merb-core/ > > dispatch/router/behavior.rb:18: warning: undefining `__send__' may > > cause serious problem > > > Any ideas? > > thanks, Jon --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/merb?hl=en -~----------~----~----~----~------~----~------~--~---
