On Tue, Oct 11, 2005 at 11:24:49AM +0200, Jonathan Weiss wrote: > Cheers, > > > I itegrated Rubygems (a package manager for Ruby libs and apps, think of > Perl CPAN or PHP Pear) into the ports tree. > > The main port, devel/ruby-gems, gives you the management program (gem) and a > module Makefile for all the rubygem-* ports.
Why not just add a CONFIGURE_STYLE target for 'ruby gem' and merge all the functionality into ruby.port.mk. I don't see the point of adding another MODULE for this. I've already shown some diffs to Damien that extend ruby.port.mk to allow creating packages for ruby libs that use install.rb, or extconf.rb or setup.rb or whatever system the ruby "cool kids" are using this week. At least in this way we get the benifit of knowing that ALL of the build logic for ruby can be found in one .mk file. > A rubygem module can then be installed like a normal port/package: > > # cd /usr/ports/devel/rubygem-rake && make install clean-depedens > Or > # pkg_add rubygem-rake-0.6.2.tgz > > I also created several rubygem-* ports for rails, but I want to wait for the > 1.0 release. I also would prefer to see all of these ports just have the regular ruby-* prefix. Once again I don't see the point of differientiating between ruby libraries that come from one ruby packaging scheme or another. I will have more comments and diffs once I have posted my version of the ruby update. -- Mathieu Sauve-Frankel
