Default PYTHON_PKGNAMEPREFIX and dropping PYTHON_PKGNAMESUFFIX

Dear all, most python ports, which install into PYTHON_SITELIBDIR or PYTHON_LIBDIR use an explicit PKGNAMEPREFIX assignment to mark the resulting packages as related to a specific python version. The porter's handbook also outlines that ports should stick to this practice. I would like to force

Re: Default PYTHON_PKGNAMEPREFIX and dropping PYTHON_PKGNAMESUFFIX

Marcus von Appen wrote on 21.01.2014 14:48: Dear all, most python ports, which install into PYTHON_SITELIBDIR or PYTHON_LIBDIR use an explicit PKGNAMEPREFIX assignment to mark the resulting packages as related to a specific python version. The porter's handbook also outlines that ports should

Re: Default PYTHON_PKGNAMEPREFIX and dropping PYTHON_PKGNAMESUFFIX

On, Tue Jan 21, 2014, Ruslan Makhmatkhanov wrote: Marcus von Appen wrote on 21.01.2014 14:48: Dear all, most python ports, which install into PYTHON_SITELIBDIR or PYTHON_LIBDIR use an explicit PKGNAMEPREFIX assignment to mark the resulting packages as related to a specific python