Am Samstag, den 11.01.2020, 15:44 -0500 schrieb Sam Hartman: > > > > > > "Daniel" == Daniel Leidert <dleid...@debian.org> writes: > > Daniel> Why not simply introduce a non-Cron-related variable in > Daniel> /etc/default/spamassassin like ENABLE_UPDATES and add it to the > new > Daniel> configuration file. You can even remove the CRON variable from > the shipped > Daniel> configuration file. This variable should take precendence over > CRON if both are > Daniel> enabled. This would have the advantage of not polluting the > meaning of CRON. It > Daniel> lets the user decide at install time, how to proceed (and if to > keep the > Daniel> previous behavior), it would ship a new default like you seem to > wish, and it > Daniel> would realize the suggestion by Philip. There is IMHO no need to > create another > Daniel> file. > > Your proposal has the negative effect of giving users who have simply > enabled the cron script an ugly conffile update message.
It was the intention of Philip's suggestion to handle it via conffile change/prompt (as an alternative to my debconf suggestion). Why do you consider a conffile prompt "ugly" or "negative"? What is your suggestion? Regards, Daniel
signature.asc
Description: This is a digitally signed message part
