How to package .pyc files
Willem Jan Withagen
wjw at digiware.nl
Sat Sep 5 10:23:37 UTC 2020
On 2-9-2020 11:14, Willem Jan Withagen wrote:
> On 2-9-2020 06:46, Kubilay Kocak wrote:
>> On 1/09/2020 4:46 am, 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?
>>
>>
>> Yes, just add them to pkg-plist (while using USE_PYTHON=autoplist to
>> handle the rest automatically)
>>
> I read that it also requires distutils, which overrules do-build and
> do-install.
> But I'm wondering how that works together with CMake building.
> Fixing the works with python using the options would be nice, since it
> is quite a hassle atm.
>
> Guess I'll have to try it to find out.
Have now: USE_PYTHON= cython py3kplist autoplist
The magic seems to work.... Nice work.
The only (wierd) thing is that there is a lot of cython files named
something like:
%%PYTHON_SITELIBDIR%%/ceph/deployment/__pycache__/drive_group.cpython-37.pyc
And replacing the 37 with %%PYTHON_VER%% does not seem to work, although
those things
are closely matched to the python version.
--WjW
More information about the freebsd-python
mailing list