Date: Mon, 31 Aug 2020 22:35:20 +0200 From: Willem Jan Withagen <wjw@digiware.nl> To: Gleb Popov <arrowd@freebsd.org>, python@freebsd.org Subject: Re: How to package .pyc files Message-ID: <d50dae56-eba8-6468-7621-ef97ef15d671@digiware.nl> In-Reply-To: <CALH631n3GeN9Jios-kiODLcxq63ckmZLRngA63VR86UpANar3Q@mail.gmail.com> References: <CALH631m7qWS7aiLhi8kFeZx0pOTU7KFjy8CHoe1VJ2zqvtdZWA@mail.gmail.com> <CALH631n3GeN9Jios-kiODLcxq63ckmZLRngA63VR86UpANar3Q@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 31-8-2020 20:46, Gleb Popov wrote: > On Mon, Aug 31, 2020 at 9:45 PM Gleb Popov <arrowd@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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d50dae56-eba8-6468-7621-ef97ef15d671>