Date: Sun, 31 Aug 2014 07:16:47 +0000 From: bugzilla-noreply@freebsd.org To: gnome@FreeBSD.org Subject: [Bug 188856] devel/py-gobject3 doesn't install on powerpc64 Message-ID: <bug-188856-6497-rwBCO8GHBF@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-188856-6497@https.bugs.freebsd.org/bugzilla/> References: <bug-188856-6497@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=188856 Kubilay Kocak <koobs@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |koobs@FreeBSD.org --- Comment #5 from Kubilay Kocak <koobs@FreeBSD.org> --- Having looked at this with Justin ... Ultimately, we probably want a FreeBSD specific block in here if there is a convention that can be relied on now and into the future, and is better than, more reliable or beneficial than: http://hg.python.org/cpython/file/70990e795657/Lib/distutils/util.py#l67 Until then, or unless there's a more canonical or conventional way for gobject to be deriving and generating egg-info, it looks like %%MACHINE%% in pkg-plist might be the way to go, at least in the immediate term. Having said that, I also can't see or find any other ports special casing this mechanism for egg-info directory name generation, and that raises a flag. >From a Python@ point of view, finding a root cause fix, that is upstreamable (if applicable) is highly desirable. -- 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-188856-6497-rwBCO8GHBF>