2008/10/26 maxbaroi <[EMAIL PROTECTED]>: > > I installed mongrel and everything worked out fine. I can see the merb > page on port 4000. I guess gem 1.2.0 didn't install mongrel when I > installed merb
Since most of exception you got here are from rubygems, I think we should catch them in dependency loading code and output something more friendly. Every time someone has the same problem, I personally bitch at "damn helpless software engineers of the 21 century, who call themselves 'Ruby rockstars' but hardly can even read an exception trace and never read the source code of essential Ruby software like RubyGems". But I cannot be sure that you have any technical background at all so... :) If you have any ideas on what error messages you'd like to see (say "Hey, Merb cannot load gem so and so, do the following to install it. For the list of common gotchas with some common gems see wiki page at ..."), just leave a reply in this thread. Again, I'd like to stress that Merb pushes RubyGems to it's limit even when it comes to error messages. But it only should help us make RubyGems better for everyone in the future. So it's not a Dependency Hell (does it sound like a movie title to you too?) but a Growth Period instead. -- MK --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
