[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: migration from cron.daily to systemd timers



Daniel Leidert <dleidert@debian.org> writes:

> Am Mittwoch, den 08.01.2020, 08:17 +0100 schrieb Philip Hands:
>
> [..]
>> How about modifying the shipped /etc/default/spamassassin to include a
>> comment explaining what's going on, and how to enable the timer instead?
>
> It seems I misread this part at first. Is it your suggestion to keep the
> default behavior and explain how to enable the timer instead?

My suggestion was simply that by modifying the file, one provokes a
question on upgrade about whether the administrator wants their modified
version (presumably modified to have CRON=1 set) or the new one from the
maintainer (now with a nice comment about what's new, that should be
enough to give the admin all the information they need).

If a system has an unmodified file (so with CRON=0, among other things)
then it gets quietly upgraded to the one with a comment, which might
even turn out to be useful, when someone used to the old ways of doing
things goes to set CRON=1 and gets the chance to learn something new.

I don't really care what that comment says, as that's up to the
maintainer of the package, and how they intend to deal with this in the
future, but I'm really not a fan adding unnecessary questions to debconf.

Cheers, Phil.
--
|)|  Philip Hands  [+44 (0)20 8530 9560]  HANDS.COM Ltd.
|-|  http://www.hands.com/    http://ftp.uk.debian.org/
|(|  Hugo-Klemm-Strasse 34,   21075 Hamburg,    GERMANY

Attachment: signature.asc
Description: PGP signature


Reply to: