https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196326
--- Comment #3 from John Marino ---
Granted, but that doesn't mean it's impossible to fix at the framework level.
Maybe it is, but has anyone looked?
I've recently fixed a port that built in stage, but I agree it would have to be
a fix t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196326
--- Comment #2 from Antoine Brodin ---
I guess this is an upstream problem, that "rubygem install" does build stuff.
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194389
Sunpoet Po-Chuan Hsieh changed:
What|Removed |Added
Status|New |Closed
Resolution
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196326
--- Comment #1 from John Marino ---
Can a ruby person comment on this PR?
I know rubygem's are not the only ports violating the "don't build in stage"
rule, but it needs to be fixed. Is anybody trying to make rubygems behave?
--
You are
Dear port maintainer,
The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated, you
