Date: Mon, 27 May 2019 06:37:55 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 237884] graphics/py-cairocffi: Update to 1.0.2 Message-ID: <bug-237884-21822-hRhQZ2cxpY@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-237884-21822@https.bugs.freebsd.org/bugzilla/> References: <bug-237884-21822@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237884 --- Comment #13 from Kubilay Kocak <koobs@FreeBSD.org> --- (In reply to Eric Turgeon from comment #11) These files end up in: %%PYTHON_SITELIBDIR%%/cairocffi/_generated/ffi_pixbuf.py %%PYTHON_SITELIBDIR%%/cairocffi/_generated/ffi.py I don't understand what " With x11-wm/qtile and x11/py-xcffib my workaround is to put those in pkg-plist" means, in context to this port being updated to 1.0.2 If it's that certain files in qtile or xcffib need to be added to their respective pkg-plist, that's due to https://github.com/tych0/xcffib/issues/92 which is probably a symptom/result of https://github.com/Kozea/cairocffi/issues/108 Either way, supplementing the autoplist with specific entries that are missing is going to have to happen for any cffi based ports until the underlying root cause bug(s) are resolved. Apart from the above that have workarounds identified, what are the blockers to updating this port, if any? -- You are receiving this mail because: You are on the CC list for the bug.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-237884-21822-hRhQZ2cxpY>