On Tue, Feb 2, 2016 at 1:21 PM, Kubilay Kocak <ko...@freebsd.org> wrote:
> 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
>
>
Hello,
This change was already mentioned in the commit log.
Since USES=python was relaxed form python 2.x only to both python 2.x and
3.x, PLIST_FILES should be updated as well.
Regards,
sunpoet
_______________________________________________
freebsd-python@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-python
To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"
