Thomas Ward via Mailman-users writes:
Would it be preferred to have a section for "Install from Git Master" or a "Install development branch" section under Installation that addresses this?� If so I can work to edit the site docs to make such sections.
I appreciate the thought, but I don't think it's useful in the general audience documentation. Installing from HEAD is always risky, especially for people using LTS distributions. The Django situation is always fraught.
Putting that recipe as is in the developer docs also doesn't make that
much sense to me, as developers are expected to have full clones of
the components they're working on. On the other hand something that
points at the dev's local repos of the Mailman Suite components does
make a lot of sense to me. Then you can add a note that "if you're
only interested in some of the components, you can automatically get
HEAD installations by substituting "https://gitlab.com/mailman/" for
your "/path/to/local/repos/" in the pip commands for the rest. That
makes sense to me because it means you don't have to keep a local
mailmanclient clone up-to-date just to work on Postorius. And
exercise for the reader: you can get your buddy's django-mailman3
hacks the same way.
What do y'all think?
Oh, yeah, probably ought to check the requirements.txt DAG to order the pip commands so that you're not overwriting PyPI versions with git master HEAD versions all the time.
Steve
On 2026-03-30 07:39, Thomas Krichel wrote:
pip install git+https://gitlab.com/mailman/mailman@master git+https://gitlab.com/mailman/mailmanclient@master git+https://gitlab.com/mailman/mailman-hyperkitty@master git+https://gitlab.com/mailman/hyperkitty@master git+https://gitlab.com/mailman/django-mailman3@master git+https://gitlab.com/mailman/postorius@master git+https://gitlab.com/mailman/mailman-web@master
-- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan