On Fri, Nov 11, 2011 at 3:31 PM, Stanislav Sedov <s...@freebsd.org> wrote: > Hi! > > The gem version distributed in ruby 1.9 is too old for some ports, > so FreeBSD uses the rubygem from ports instead. To get the gem > command back just install the ruby-gems port. > > -- > Stanislav Sedov > ST4096-RIPE > > () ascii ribbon campaign - against html e-mail > /\ www.asciiribbon.org - against proprietary attachments
Thanks for the timely reply. That's exactly what I did after posting my question--I installed the gems port and the rake port (rake suddenly disappeared as well). Please forgive me now as I express my frustration and dislike over the sudden disappearance of executables: <vent> I quite DISLIKE this as the "solution". Updating ports and rebuilding the same version of a port that's been in the tree for a long time SHOULD NOT suddenly remove a common executable that those relying on the port have come to expect to be present WITHOUT A BIG GIANT IMPOSSIBLE TO IGNORE WARNING while building or installing the port. This breaks so many automated scripts I have. How I get to update each one to check for the additional ports. UGH!!!! I HATE IT! I much prefer to update gems and rake on my own systems NOT using FreeBSD ports using "gem update --system && gem update" </vent> Thank you for your time and thank you for permitting me to vent on this topic. Sincerely, Aaron Gifford _______________________________________________ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
