Created attachment 190170 [details]
Initial submission of GNU Mailman 3 into the ports tree. See review D14126.
Comment on attachment 190170 [details]
See Phabricator for updated patch.
Now that the zope dependency has hit the tree, will you update this to 3.2 ?
(In reply to Kurt Jaeger from comment #2)
I have 3.2 built locally with updated port files and such. Still need to do runtime testing.
Furthermore, there is a hard dependency on databases/py-sqlalchemy12, but another hard dependency databases/py-alembic specifies databases/py-sqlalchemy10. I locally patched databases/py-alembic to use databases/py-sqlalchemy12 to facilitate building and runtime testing, but anything further is a topic for another PR.
Phabricator review D14126 refreshed, updated to 3.2.0, with inline questions. Still QAing runtime on my end but the port-plumbing should be somewhat sane now.
What is the state of this port? It is not yet in the official ports tree.
I would prefer to have a port instead of installing it with Ansible from the Git sources.
Can I help somehow with the process? What would be needed?
(In reply to Daniel Winter from comment #5)
I have an update to 3.2.2 waiting in the wings in my local ports repo. As with the initial 3.2.0 efforts, paths need to be checked, and patched if necessary, to follow our hier(7) as upstream hardcodes many paths to the Linux layout (and USES=pathfix won't automatically get them). Other than that, I still need to test runtime itself.
Charlie, what's the state of your efforts from comment #6?
Now that python2 is EOL, having mailman3 in ports becomes critical. Is there a way to bump the priority of this, perhaps someone can take it upon themselves to finish the port? Or are "nobody" using mailman these days?
testbuild with the most recent version from the review, updated to 3.3.0, builds fine.
TODO: more run-tests, path fixes as requested in the review.
any updates on this? I'm eagerly waiting for this port to upgrade our Mailman instances here ... thanks :-)
(In reply to Julien Cigar from comment #11)
No updates, we still need run-tests.