Re: one package altering other package's postrm
On 2014-12-15 15:56, Alexandre Detiste wrote:
>> Having various cron daemon implementations follows from their differing designs,
>> but there isn't much design to merely writing out a file to a specific directory securely.
>
> I agree.
>
> bcrontab does special magic and talk to it's deamon with a socket.
Yes, I completely forgot about this. A similar feature was also
requested for regular cron. The socket approach avoids the need for a
setgid helper, which is nice...
>> TBH, I'd expect such a cron-base package to be provided by src:cron,
>> which already ships these files.
>
> That would be great !
>
>> It's merely a matter of splitting the
>> current binary package into two separate ones.
>
> Or three, to take care of bcron-run quirks:
>
> - cron-base : /etc/{ crontab | cron.d | hourly | daily | weekly |
> monthly } : this would be used by all cron-daemons
>
> - crontab : owner of /var/spool/cron/crontabs , /etc/cron.allow ,
> /etc/cron.deny : this would be shared by cron & systemd-cron
> (the two files /etc/cron.allow & /etc/cron.deny really
> belong to crontab, they are not used by the deamon)
>
> - cron, that depends on cron-base & crontab
Agreed!
Reply to: