[MacPorts] #43830: rb-rubygems

[MacPorts]

#43830: rb-rubygems
-----------------------------+-----------------------
  Reporter:  mschamschula@…  |      Owner:  mr_bond@…
      Type:  defect          |     Status:  new
  Priority:  Normal          |  Milestone:
 Component:  ports           |    Version:  2.3.0
Resolution:                  |   Keywords:
      Port:  rb-rubygems     |
-----------------------------+-----------------------

Comment (by egall@…):

 Replying to [comment:5 and.damore@…]:
 > It seems the issue here is assuming that 'gem' is the correct command to
 call, it could be a widespread habit but is having a 'gem' binary
 mandatory?
 >
 > Anyway this should be solved by just probiding a ruby_select port rather
 than augmenting post-install in each of rb-rubygems|ruby19|ruby20.
 >
 > ''edit'':
 > I see there's ruby_select already.

 I don't really see how the ruby_select port could deal with the `gem`
 binary, considering that the `gem` binary is from a different set of ports
 than the set that the `ruby_select` port is used with... Maybe that is
 something the `select` PortGroup could be modified to deal with? That way,
 besides dealing with this issue, we also would no longer need to have a
 different `_select` port for every single python port that has binaries
 that people might want to use un-suffixed-ly, like we do now (as brought
 up in comment:ticket:38016:1 for example). Then again, I suppose the
 `select` PortGroup is already complicated enough as it is...

-- 
Ticket URL: <https://trac.macports.org/ticket/43830#comment:6>
MacPorts <http://www.macports.org/>
Ports system for OS X