Date: Tue, 31 Oct 2017 17:31:29 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 219641] devel/py-qt5-core: Fails to package/install, incorrect pk-plist entries Message-ID: <bug-219641-21822-StqJAHtCXX@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-219641-21822@https.bugs.freebsd.org/bugzilla/> References: <bug-219641-21822@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=3D219641 --- Comment #26 from Mikhail T. <mi@ALDAN.algebra.com> --- Comment on attachment 187619 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D187619 Fix py-qt5-* with python3 > +USE_PYTHON=3D py3kplist Why is `py3kplist' necessary, if `autoplist' was not necessary for the regu= lar case of Python-2.7? The comment inside python.mk confuses me: # py3kplist - Automatically generates Python 3.x compatible # __pycache__ entries from a Python 2.x packaging l= ist # when defined. Use this for ports that do *not* use # standard Python packaging mechanisms such as # distutils, and support *both* Python 2.x and 3.x. # Not needed, if USE_PYTHON=3Dautoplist is set. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-219641-21822-StqJAHtCXX>