On 01/04/2018 08:34 AM, Chris PUCHALSKI wrote:
> It is a Redhat package (mailman-2.1.12-25.el6.x86_64) so not from source. I
> have the version locked because I found updates over wrote the customizations
> made to the look/feel. Most of the modifications are related to hiding
> options from use
On 01/04/2018 01:01 PM, Lindsay Haisley wrote:
> Also, since group assignments, file locations, etc. are still somewhat
> distribution-specific for Mailman, it would be helpful if the standard
> build would include an executable binary, e.g. "mailman-config", which
> would simply spit back the com
On Thu, 2018-01-04 at 11:30 -0600, Dimitri Maziuk wrote:
> On 2018-01-04 11:06, Stephen J. Turnbull wrote:
>
> >
> > As I understand your
> > post, RH/Centos leaves mm_cfg.py in /var/lib/mailman/Mailman and puts
> > a link in /etc. But Debian moves the actual file to /etc/mailman, and
> > puts a
On 2018-01-04 11:06, Stephen J. Turnbull wrote:
As I understand your
post, RH/Centos leaves mm_cfg.py in /var/lib/mailman/Mailman and puts
a link in /etc. But Debian moves the actual file to /etc/mailman, and
puts a link in /var/lib/mailman/Mailman. Almost surely people are
going to end up wit
Dimitri Maziuk writes:
> Fair enough but I should think expecting site-specific settings to
> live under /etc is no longer distro-specific and that mm_cfg.py
> violates the principle of least surprise for any distro since
> fsstnd.
Fair enough, but the distros already have scripts that handle
It is a Redhat package (mailman-2.1.12-25.el6.x86_64) so not from source. I
have the version locked because I found updates over wrote the customizations
made to the look/feel. Most of the modifications are related to hiding options
from users (to protect themselves) and cosmetic (so it fits com
