From: "Mauricio Fernández" <mfp@...>
Date: 2005-07-22T03:19:58+09:00
Subject: Re: Rubygems now integrated in the FreeBSD ports tree


Hi,

On Fri, Jul 22, 2005 at 01:39:00AM +0900, Jonathan Weiss wrote:
> Cheers,
> 
> I integrated rubygems into the FreeBSD ports tree.
> 
> You now can do a
> 
> # cd /usr/ports/www/rubygem-rails
> # make install clean
> 
> That means that the user is now able to manage gems through the ports tree
> and does not have to also use the gem command.

I have been reading http://www.freebsd.org/cgi/query-pr.cgi?pr=82397 and
have a number of questions, esp. about how this would work in practice
from the FreeBSD developer's point of view. Also, please feel free to
correct me if any of the following info is inaccurate.

If I understand

do-install:
       ${RUBYGEMBIN} install --install-dir ${PREFIX}/lib/ruby/gems/${REV} \
       ${PORTSDIR}/distfiles/rubygem/${PORTNAME}-${PORTVERSION}${EXTRACT_SUFX}

correctly, ports essentially end up calling gem to install a .gem file placed
in ${PORTSDIR}/distfiles/rubygem/.

If so, 
* Is it possible to apply patches to RubyGems packages? What if the
  RubyGems package differs substantially from the pristine sources (e.g.
  if there's a complex build process using for instance a Rakefile,
  probably with some source code massaging)... wouldn't that case
  complicate patching?
* Don't you have to create the Makefile, distinfo, pkg-descr and
  pkg-list (at least in part) manually for every single version released
  through RubyGems?
* If the answer to the previous question is affirmative, this means that
  newly released RubyGems packages won't be available through the ports system
  until a FreeBSD developer generates the pertinent data, right?
* RubyGems packages installed via ports interfere with those installed
  directly with  gem install, don't they?
* User scripts need to  require 'rubygems' or set RUBYOPT to load
  RubyGems packages installed via ports, right?

Thanks in advance for the answers,

-- 
Mauricio Fernandez