Re: one package altering other package's postrm

[Ian Jackson <ijackson@chiark.greenend.org.uk>]

Guillem Jover writes ("Re: one package altering other package's postrm"):
> As mentioned before, just add a versioned Breaks against the cron
> package not supporting that, do not mangle its maintainer scripts.
...
> If using current apt with APT::Get::Purge=true or --purge, or the
> aptitude TUI and marking cron for purge, the conflicting package will
> get purged before the other package is even in the picture.

Isn't this combination rather dangerous ?  The result would appear to
be that switching to systemd-cron would first purge the cron package,
discarding any local changes to /etc/crontab (and other config files
owned by cron).

Ian.