Date: Mon, 31 Aug 2020 22:46:23 +0400 From: Gleb Popov <arrowd@freebsd.org> To: python@freebsd.org Subject: Re: How to package .pyc files Message-ID: <CALH631n3GeN9Jios-kiODLcxq63ckmZLRngA63VR86UpANar3Q@mail.gmail.com> In-Reply-To: <CALH631m7qWS7aiLhi8kFeZx0pOTU7KFjy8CHoe1VJ2zqvtdZWA@mail.gmail.com> References: <CALH631m7qWS7aiLhi8kFeZx0pOTU7KFjy8CHoe1VJ2zqvtdZWA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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. Any ideas?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CALH631n3GeN9Jios-kiODLcxq63ckmZLRngA63VR86UpANar3Q>