Date: Fri, 11 Nov 2011 16:52:07 -0700 From: "Aaron D. Gifford" <astounding@gmail.com> To: ruby@freebsd.org Subject: Re: What changed? (gem command missing in 1.9) Message-ID: <CAGDxMR51-yk0fUOdBUBmEC1ntXS2eA-QEpkS5Ymtp95jf0u7mw@mail.gmail.com> In-Reply-To: <CAGDxMR4P3TiJkTkk4o=gTW5-Hj6my2bsgc9j6aX=EwanPJ0MNw@mail.gmail.com> References: <CAGDxMR66_1GexKFbN2bu9%2B-T%2BrxJ-UHW5WsfLJQvqMG7M=m66A@mail.gmail.com> <20111111143115.5bf5d195.stas@FreeBSD.org> <CAGDxMR4P3TiJkTkk4o=gTW5-Hj6my2bsgc9j6aX=EwanPJ0MNw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I'm not familiar with the inner workings of FreeBSD's port system, but is it possible that issues like 'gem' and 'rake' suddenly no longer being part of the lang/ruby19 port (due to the aforementioned outdated versions) could be dealt with during some sort of post-install hook while installing the lang/ruby19 port, a hook that could then install devel/ruby-gems and devel/rubygem-rake ports so that the executables that previously were always part of lang/ruby19 will still be automatically installed with that port? Speculating, Aaron out.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGDxMR51-yk0fUOdBUBmEC1ntXS2eA-QEpkS5Ymtp95jf0u7mw>