[Pkg-mailman-hackers] Bug#502263: Bug#502263: mailman: policy violation (9.1.1): writes to /usr when config changes

[Helmut Grohne]

> I welcome input on this issue from people with more deep knowledge than
> myself about these Python cached files, and how we could best address it
> in this case. If there's a straightforward solution I think we can apply
> it for lenny.

The simplest solution might actually be to take the approach
python-support uses.

1) The .py files stay where they are.
2) They are symlinked to a directory hierarchy within /var/lib. (This
   means directories are copied and files are symlinked.)
3) The .pyc files will get created on /var.
4) The module path has to be adapted from /usr/lib/mailman to something
   on /var. Therefore /usr/lib/mailman/bin/paths.py should be adapted.

> However I indeed don't think this should be release critical, as you say,
> it doesn't break when writing fails. It is an inconvenience with e.g.
> tripwire, but that is resolvable within the context of that application.
> So I would classify it as an 'important' issue myself.

ACK.

Helmut