Arthur Korn wrote:
>
> Hi
>
> Rene Mayrhofer schrieb:
> > There's only one minor problem: Shipping files for
> > update-modules is easy, since modutils is required and
> > therefore /etc/modutils should always be present. But since
> > logcheck is only optional, should packages still ship files in
> > /etc/logcheck/*.d/ although they will not be used if logcheck
> > is not installed ?
>
> Yes, they should be installed. If the user installs logcheck
> after he installed a package containing some files in
> /etc/logcheck/*.d/ it will just work.
>
> There are many examples where this is done already, eg
> /usr/lib/menu/, /etc/devfs/*.d, /etc/X11/Xsession.d,
> /etc/emacs/site-start.d, /etc/ppp/ip-{up,down}.d,
> /etc/network/if-pre-up.d, /etc/network/if-up.d,
> /etc/network/if-down.d, /etc/network/if-post-down.d,
> /etc/logrotate.d, /etc/apm/resume.d, /etc/apm/suspend.d,
> /etc/apm/event.d.
Thanks for pointing this out. In this case, my next major logcheck release will
include those /etc/logcheck/*.d/ directories and packages can start plugging
files in there. Another small question: Is it better to have different .d
directories (for ignore, violations, violations.ignore and hacking) or having
one .d directory and using filename-postfixes (e.g. postfix.ignore,
postfix.violations, postfix.violations.ignore, postfix.hacking). In the latter
case, the handling (for logcheck) is a bit more complex and leads to errors
(files not found when the postfix is not 100% correct, ...), but does not need a
bunch of directories ?
I would prefer different directories, but I am open to any suggestions. What do
you think ?
best greets,
Rene
