I'm trying to figure out how to do PEP517 builds in ports, various newer Python ports use this instead of the old methods. Here are some key pieces.
*devel/py-flit Flit packaging tool
*devel/py-flit_core only the distribution-building parts of Flit
*devel/py-pep517 wrappers to build Python packages using PEP517 hooks
devel/py-build tool to build PEP517 packages
devel/py-installer tool to install py packages from wheel distros
*textproc/py-tomli_w TOML writer, used by Flit
Some of these ports themselves (marked with *) have a bootstrap problem
so I've used flit to generate ${FILESDIR}/setup.py files used during the
build. These can be regenerated (e.g. for updates) via the "setuppy"
maintainer target I've added in their individual Makefiles. I don't
suggest using that method in the general case for other ports (I think
we'll want some infrastructure in python.port.mk) but at a push we could
use that method if we needed to update something else before we've figured
out those parts.
At this point I'd like to import these so I don't need to keep track
of them locally while I try to figure out what else we need for
python.port.mk. OK to import?
flit_ports.tgz
Description: application/tar-gz
