Re: Re: rb-rubygems does not work

On 8/25/06, Tim Pritlove <[email protected]> wrote:
> On 24.08.2006, at 09:53, Paul Guyot wrote:
> > Le 24 août 06 à 16:16, [email protected] a écrit :

> >> 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 would love to take this step but I used "rails" just an example.
> The package I really need is "builder" where there is no port
> available yet. I tried to do one of my own but failed initially and I
> couldn't find documentation on how to design  a Ruby gem package
> Portfile properly.

if you are willing to pollute your macports install prefix, you can
*easily* accomplish this.

	jpm.giant-squid ~ -=> sudo gem install builder
	Need to update 11 gems from http://gems.rubyforge.org
	...........
	complete
	Successfully installed builder-2.0.0
	Installing ri documentation for builder-2.0.0...
	Installing RDoc documentation for builder-2.0.0...
	jpm.giant-squid ~ -=>

now that ruby 1.8.5 has been released (and perhaps the macport soon as
well), i will find out first hand exactly what paul meant by
pollution. i have many gems in my install prefix that were not
installed/tracked by macports - but maybe the assumption that the
entire prefix is managed by macports should be reconsidered? it really
seems like it should be possible to allow these two systems to coexist
without trying to duplicate the functionality of one into the other.
gem has a 'contents' command, perhaps that could be leveraged. maybe
port could have a gem command which dynamically created ports for gems
and could then track files on disk?

regards,
jean-pierre