Date: Tue, 2 Feb 2016 16:21:56 +1100 From: Kubilay Kocak <koobs@FreeBSD.org> To: Sunpoet Po-Chuan Hsieh <sunpoet@FreeBSD.org>, ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org, python <python@FreeBSD.org> Subject: Re: svn commit: r407751 - head/security/py-m2crypto Message-ID: <56B03CF4.4070200@FreeBSD.org> In-Reply-To: <201602011948.u11JmPqj003525@repo.freebsd.org> References: <201602011948.u11JmPqj003525@repo.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2/02/2016 6:48 AM, Sunpoet Po-Chuan Hsieh wrote: > + %%PYTHON_SITELIBDIR%%/M2Crypto/${PYCACHE_DIR}${PYCACHE_FILE}.pyc \ > + %%PYTHON_SITELIBDIR%%/M2Crypto/${PYCACHE_DIR}${PYCACHE_FILE}.${PYOEXTENSION} Hi Sunpoet, This change wasn't mentioned in the commit log. Could you summarise the rationale? Was it to fix a bug? Might/Do other ports need to do this too? Might there be value in having the framework bits take care of this? Reason I ask is, as we move toward reproducible builds and simplifying Python packaging, having the framework take care of compilation post-install (rather than in packaging) is a desirable target for various reasons. We also have an open task not to package pyc/pyo files: https://wiki.freebsd.org/Python [ ] Don't package (plist) or install .pyc and .pyo files. Details: https://wiki.freebsd.org/Python/CompiledPackages
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?56B03CF4.4070200>