[MacPorts] #64906: fixing Ruby for PowerPC

[MacPorts]

#64906: fixing Ruby for PowerPC
-----------------------------+-------------------------------------------
  Reporter:  barracuda156    |      Owner:  kimuraw
      Type:  defect          |     Status:  closed
  Priority:  Normal          |  Milestone:
 Component:  ports           |    Version:  2.7.2
Resolution:  wontfix         |   Keywords:  powerpc, leopard, snowleopard
      Port:  ruby27, ruby30  |
-----------------------------+-------------------------------------------

Comment (by barracuda156):

 Replying to [comment:9 kencu]:
 > So let this be a tiny lesson to people.
 >
 > If you open many tickets about little failures, the end result is the
 port is locked down to prevent you from ever trying to build it again.
 >
 > This is why you see me trying to be a bit judicious about 1000s of
 tickets being opened, and closing many of them (at least I was previously
 closing many of them).
 >
 > If you want ruby on PPC Tiger and Leopard (and as I recall it works
 quite well, almost all tests pass as above) what you do is FIX THE PROBLEM
 yourself and PR the fix into GitHub for the maintainer to commit, just
 posting that it fixed XYZ problem.
 >
 > The more you make the port look broken to people, the more likely this
 will happen to it.
 >
 > Now, you see, it will be hard to impossible to ever get ruby support
 back for PPC in MacPorts, once this decision has been made. So this is
 where you wind up.

 I get your point, but as for Ruby goes, this is the only ticket I have
 opened, and that too I did not demand anyone fix it for me and actually
 started working on it myself. While I may be guilty of unnecessary tickets
 in some cases, here I don’t see anything to justify such a response.

 On a general note, my understanding has been that having a ticket about
 existing problem is useful, as it informs anyone else interested that such
 a problem exists. How else we are to inform developers and users?
 Yes, I definitely agree that if me or anyone is able to provide a fix, it
 makes better sense to propose a fix rightaway rather than merely state
 that something is broken. However often that’s not the case, and resorting
 to developers on Github may or may not work (we know a number of cases
 when developers just don’t care).

-- 
Ticket URL: <https://trac.macports.org/ticket/64906#comment:10>
MacPorts <https://www.macports.org/>
Ports system for macOS