python33: incorrect pkg-plist

[Dmitry Sivachenko]

Am I the only person with that problem?
After python3.3.3->3.3.4 upgrade I still get this:

root:/usr/ports/lang/python33 # make package
===>  Building package for python33-3.3.4
pkg-static: lstat(/usr/ports/lang/python33/work/stage/usr/local/include/python3.3mm/accu.h): No such file or directory
pkg-static: lstat(/usr/ports/lang/python33/work/stage/usr/local/include/python3.3mm/Python-ast.h): No such file or directory
pkg-static: lstat(/usr/ports/lang/python33/work/stage/usr/local/include/python3.3mm/Python.h): No such file or directory
pkg-static: lstat(/usr/ports/lang/python33/work/stage/usr/local/include/python3.3mm/abstract.h): No such file or directory
pkg-static: lstat(/usr/ports/lang/python33/work/stage/usr/local/include/python3.3mm/asdl.h): No such file or directory
pkg-static: lstat(/usr/ports/lang/python33/work/stage/usr/local/include/python3.3mm/ast.h): No such file or directory
<...>


On 02 марта 2014 г., at 19:32, Dmitry Sivachenko <demon at FreeBSD.org> wrote:

> Hello!
> 
> Right now, python's include files are listed as follows:
> 
> %%PYTHON_INCLUDEDIR%%%%PYABIVER%%/accu.h
> 
> But both PYTHON_INCLUDEDIR and PYABIVER contain trailing "m":
> 
> # make -V PLIST_SUB
> PYVER=3.3  PYMAJOR=3  PYVER_WITHPAT=3.3.3  PYABIVER=m PYTHON_INCLUDEDIR=include/python3.3m  <...>
> 
> Thus this line in pkg-plist becomes
> include/python3.3mm/accu.h
> (double "m").
> 
> So both "make package" and "make check-orphans" report these files.
> 
> I am not sure how did this work earlier, but now it seems broken.
> 
>