I'm running debian on my mail server. I use etckeeper to track
changes in /etc.
Often I run across modules such as spamassassin-esp and maybe I would
consider playing with Jared Hall's CHAOS module.
I'm curious what the recommended best practice is to install such
modules from a git repo.
For spamassassin-esp, I cloned the repo into my /etc/spamassassin/
directory and then added this to my local.cf:
loadplugin Mail::SpamAssassin::Plugin::Esp spamassassin-esp/Esp.pm
include spamassassin-esp/Esp.cf
This allows me to 'git pull' from this repository from time to time to
update it. But it's not perfect, especially as I have local changes
to Esp.cf. It's actually worse since I forked it to give back some
changes but I'd say that's perhaps less usual.
Furthermore, as I said, I use etckeeper and when I 'apt upgrade', I get
constant warnings:
modified: spamassassin/spamassassin-esp (modified content, untracked content)
So clearly it's not ideal to clone a spamassassin module into
/etc/spamassassin!
I'm curious if someone has a clean solution here that allows updating
the module from time to time from git.
I realize this may be more a debian question and I may post it on the
debian-users list if I don't get any decent replies here.
Michael Grant
changes in /etc.
Often I run across modules such as spamassassin-esp and maybe I would
consider playing with Jared Hall's CHAOS module.
I'm curious what the recommended best practice is to install such
modules from a git repo.
For spamassassin-esp, I cloned the repo into my /etc/spamassassin/
directory and then added this to my local.cf:
loadplugin Mail::SpamAssassin::Plugin::Esp spamassassin-esp/Esp.pm
include spamassassin-esp/Esp.cf
This allows me to 'git pull' from this repository from time to time to
update it. But it's not perfect, especially as I have local changes
to Esp.cf. It's actually worse since I forked it to give back some
changes but I'd say that's perhaps less usual.
Furthermore, as I said, I use etckeeper and when I 'apt upgrade', I get
constant warnings:
modified: spamassassin/spamassassin-esp (modified content, untracked content)
So clearly it's not ideal to clone a spamassassin module into
/etc/spamassassin!
I'm curious if someone has a clean solution here that allows updating
the module from time to time from git.
I realize this may be more a debian question and I may post it on the
debian-users list if I don't get any decent replies here.
Michael Grant