Date: Sun, 04 Sep 2016 12:31:25 +0000 From: bugzilla-noreply@freebsd.org To: ruby@FreeBSD.org Subject: [Bug 196326] rubygem framework bug : building occurs in stage phase Message-ID: <bug-196326-21402-4S73RmQnPJ@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-196326-21402@https.bugs.freebsd.org/bugzilla/> References: <bug-196326-21402@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D196326 --- Comment #17 from John Marino <marino@FreeBSD.org> --- if you re-read it carefully, I said that I would work on a patch *after* the concept had been discussed so I that wouldn't waste my time. For that to happen, the "Person in charge" would have had to be revealed and the patch concept be discussed. So far, nobody, and I mean nobody, on the python team has made any sort of indication that they want to fix this flaw= or at least want to spent any time doing it. It's the python's team responsibility to fix it. I offered to do the work because python team won't. I don't want to do it. I shouldn't have to do = it.=20 Once the flaw was reported, that should have been enough to get a fix start= ed. As I said before, the safest fix appears to be to move the "rubygem install" install command into the build stage and use a temporary staging directory = (not $STAGEDIR). The install target would move the files from that temporary di= r to $stagedir. That should solve the issue without having to fix the awful rubygem native extension code. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-196326-21402-4S73RmQnPJ>