Date: Mon, 6 Feb 2023 21:29:51 +0100 From: Rainer Hurling <rhurlin@gwdg.de> To: Kurt Jaeger <pi@freebsd.org> Cc: <python@freebsd.org> Subject: Re: textproc/py-pyphen: Change build to pep517 Message-ID: <d2bebdff-afc7-fda4-cb57-1f133e3968f4@gwdg.de> In-Reply-To: <Y%2BFSc5VjajB4h/XC@fc.opsec.eu> References: <202302061004.316A4YbD001799@gitrepo.freebsd.org> <Y%2BEuDK6z344u7eRc@fc.opsec.eu> <4774f0f2-1438-56fd-69c4-b35acacdcd33@tsoft.com> <Y%2BFSc5VjajB4h/XC@fc.opsec.eu>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Kurt, Am 06.02.23 um 20:18 schrieb Kurt Jaeger: > Hi! > >> You can change any port to pep517 except in very few cases when this >> would introduce a circular dependency. >> pep517 is now a default way to build python packages because distutils >> is now deprecated in Python. >> In the case of textproc/py-pyphen - it used the ad-hoc setup.py that >> wasn't registering it properly, because this was added before pep517 was >> available. >> >> Hope this helps. > > Yes, thanks. I retested and found out that weasyprint had no DEPEND > on any of the flit* stuff. It needs it to build, but not to run. > > So it was not an issue of distutils vrs pep517. > Just for the case, you missed it ;) In https://wiki.freebsd.org/Python/PEP-517 you can read about the build backend you have to specify, if using pep517. This is mentioned in the initial commit [1], which introduces USE_PYTHON=pep517. HTH and best wishes, Rainer [1] https://cgit.freebsd.org/ports/commit/?id=cc8a1878e0242055ab6a8c20d33654451f78720e
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d2bebdff-afc7-fda4-cb57-1f133e3968f4>