Re: rb-rubygems does not work

Le 24 août 06 à 16:16, [email protected] a écrit :

> On 8/23/06, Tim Pritlove <[email protected]> wrote:
>
>> So far no success. All ruby ports I install via "port" do go into the
>> specified directory, but the gem command keeps on complaining
>
> the end goal is to install rails, no? even if it isn't, i would
> recommend james duncan davidson's "Sandboxing Rails with Darwin Ports"
> article:
> 	<http://duncandavidson.com/essay/2006/04/portsandbox>

You shouldn't do this.

Instead, do:
sudo port install rb-rails

> i have used it several times and haven't had any problems (although
> this morning i found that the mysql5 port seems hosed on ppc/10.4.7 -
> didn't have that problem on intel last week). i routinely install via
> RubyGems and follow james' advice to use port to install ruby
> libraries that depend on native code and RubyGems for pure ruby stuff.
> it seems a little strange to have a macport for every ruby gem though
> doesn't it - how meta.

I disagree. We should have a macport for every ruby gem and you  
should use them.
For two reasons:
#1 using gem will pollute /opt/local
#2 using MacPorts allow you to safely remove gems.

Besides, as I explained recently here, it's extremely simple to build  
a portfile for a gem with the recent addition of the gem option for  
the ruby PortGroup.

Paul
-- 
Ministre ultraplénipotentiaire en disponibilité.
Mobile. Sans baignoire fixe.
http://www.kallisys.com/
http://www-poleia.lip6.fr/~guyot/