Created attachment 223894 [details] New port files security/py-cryptography has started using rust in its code. It uses the new setuptools-rust extension to compile the rust code in the setup.py build step. I'm not sure how to work with new (releases of) setuptools-* ports; When upgrading this port, py-cryptography does not get rebuild. https://github.com/PyO3/setuptools-rust
This is a new port request so the auto assignment mechanism must be confused.
Based on https://github.com/PyO3/setuptools-rust/blob/main/setup.cfg#L29-L30 this PR should depend on 255341, as it needs setuptools>=46.1
Hey any update on when this will get added? I'd like to add the etebase/etesync ports, but they require this port as a prerequisite. Thanks!
Given the size and complexity of the rust stack, it'd be great to get QA (needs-qa) confirmation (with poudriere) across all tier archs and supported freebsd versions. Anyone can do this, though maintainer preferred (so they're across it), and if anyone needs help: #freebsd-ports on Libera IRC or #ports on Discord and we can help you get poudriere running if you dont have it up already.
Can I help out? I'm currently running a single variation on poudriere (FreeBSD 12.3 + Python 3.9 + amd64). And I haven't moved to tracking freebsd-ports with git. I'm still stuck on a private mercurial repo that follows upstream with git and rsync. I could add a new git clone and track the public freebsd-ports git. Or is there some workspace for this on reviews.freebsd.org?
I see that setuptools-rust exists in ports and is up-to-date as of Feb 28th: https://cgit.freebsd.org/ports/commit/?id=601ebcdc2ba0418f9377e2962e5836964841bdb1 Looks like this issue can be closed?