Hi Jon, We're using the Gem::DependencyInstaller directly in our tasks, so we don't shell out to the system for this; there are good reasons for doing so.
In merb.thor you will find :user_install => false, quite explicitly disabling what you desire. The single most important reason for doing this, is that when people forget 'sudo' the gems will end up in ~/gems without them even knowing. Once this happened, ~/.gems will be added to the gem load path until the dirs in there are removed. With merb, we believe things should happen in a consistent manner, and when needed, people should be explicit about their goals. The default RubyGems behaviour is considered harmful. Also, we don't have the gem install path hardcoded, if it's not explicitly set, RubyGems will figure it out. Except for :user_install => false of course... I encourage you to have a look at: http://wiki.merbivore.com/howto/installation/thor For example: thor merb:stack:uninstall This will do exactly what you want, without trying to install into ~/.gems in the first place; apparently this is the reason why you've asked for this functionality; I disagree that gems isn't the most robust solution btw - adopting rubygems in merb gives us serious advantages. - Fabien --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
