Fabien, Your are joking, right? If you think some people don't like to install things local to a user, then maybe you only grok about 10% of the concept that Unix based systems are multiple user operating systems. I realize many have full superuser access and treat the entire system as a playground and install files all over the place. I am not one of those users. Further, I do not want various gem bin files thrown in my /usr/bin. I only run ruby apps from one user, It is prudent to have them installed local to that user. Even if I did run ruby apps from more than one user, I would setup the shared files accessible to a group and have the several users belong to this group.
Are you aware that some gems don't uninstall well? Not sure what the issue is but I run into it quite a bit. So if I have to manually uninstall a gem, what files do I delete? Well, having them all under ~/.gem does help a lot in knowing that even the bin files were put there. ~/.gem does not lead to confusion, unless of course you can't read. A gem based install purposely outputs a nice message letting you know its putting the gem in ~/.gem if you don't run it as a superuser. Also, gems has config settings and you could even change this if you like. Merb is supposed to be gem based. If so, you must allow the user to instlll the generated gems with the same rules as they would install any gem they get from rubyforge. I just woke up, so maybe I'm not in the mood for jokes. You were joking when you said this is a feature, right? Seriously, you are packaging gems, so after you package it, hand off the "install" part of the gem to the gem tool itself and let it use rules that a gem user would expect it to follow. thanks, Jon On Oct 15, 4:23 am, loob2 <[EMAIL PROTECTED]> wrote: > Hi Jon, > > It's not a bug, it's a feature! ;-) I've deliberately chosen not to > support ~/.gem based gem installation since it will inargueably lead > to confusion. > > People expect these gem directories to be available: system gems and > bundled gems. Most users aren't aware of this third, invisible(!), gem > install path and having gems installed there tends to cause a lot of > trouble. > > - Fabien > > > This makes sense as I didn't run the command with sudo. And I didn't > > want to. When I use "gem install blah" it will install blah into > > ~/.gem/ instead of the system global location. This is what I want, > > to have the gems installed only for this user. So gems is doing the > > correct thing. But the thor scripts are not respecting this well > > known behavior. > > > I supposed this is a bug? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
