On 04/20/2016 01:11 AM, Andrew Hodgson wrote:
My next stab at this was going to be using venvs, but creating the venv as the directory /opt/mailman which gives cleaner paths (to my mind anyway), but haven't got round to doing it yet.
You should be aware that mailman-bundler uses two venvs, one for Python 2 and one for Python 3. The idea is you create the Python 2 venv and activate it when running mailman-bundler's buildout, but that process will also create a venv-3.x venv in the bundler directory.
I think what may make sense is to clone mailman-bundler directly into /opt/mailman rather than /opt/mailman/mailman-bundler. Then follow the docs from there. This should give you paths like /opt/mailman/venv/, /opt/mailman/venv3.x/, /opt/mailman/deployment/, /opt/mailman/mailman-web/, /opt/mailman/bin/, /opt/mailman/var/ and so on without the extra mailman-bundler/ level.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan