How to package .pyc files

Willem Jan Withagen wjw at digiware.nl
Mon Aug 31 20:35:24 UTC 2020


On 31-8-2020 20:46, Gleb Popov wrote:
> On Mon, Aug 31, 2020 at 9:45 PM Gleb Popov <arrowd at freebsd.org> wrote:
>
>> Hello. I'm fiddling with the devel/mercurial port (
>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242463 ). The current
>> Makefile results in
>>
>> Error: Orphaned: %%PYTHON_SITELIBDIR%%/mercurial/__modulepolicy__.py
>> Error: Orphaned:
>> %%PYTHON_SITELIBDIR%%/mercurial/__pycache__/__modulepolicy__.cpython-37.opt-1.pyc
>> Error: Orphaned:
>> %%PYTHON_SITELIBDIR%%/mercurial/__pycache__/__modulepolicy__.cpython-37.pyc
>>
>> errors. However, adding these files into pkg-plist seems a bit hard - it
>> requires %%PYTHON_VER%% subst and a special treatment for python2 case.
>> Which made me wonder - should these files be packaged at all? If yes, maybe
>> there is some simple solution I'm missing?
>>
>> Thanks in advance.
>>
> Inspecting ${WRKDIR}/.PLIST* files after the build revealed that all other
> .pyc files are correctly added to the plist. So, there is something special
> about this __modulepolicy__.py file. I'm tempted to simply remove it on
> post-install.
Had the same in the ceph port.
I just kicked them.... I've spent a long weekend getting things in, to 
no avail.
And python will recreate them if needed.

--WjW



More information about the freebsd-python mailing list