On Tue, Jan 11, 2000 at 11:13:11PM +0000, Julian Gilbey wrote: > Let's say cron's maintainer decides to convert > /etc/cron.daily/standard to use logrotate, in concordance with the > current policy manual.
Which he's said isn't likely. Hmm... > So he makes cron Depend on logrotate, requiring logrotate to become > an important package (cron is important). Now logrotate will > basically be present on every up-to-date Debian system and packages [..] > So this argument is basically spurious as long as we make logrotate > important. Just because a package is in important doesn't mean that it will be installed. If I install sendmail, I don't have exim, which is in important... In your argument, logrotate will be installed iff cron is installed, which is a fair bet. But why force cron to be the trigger? If a package expects logrotate to be present, as shown by it providing an /etc/logrotate.d/* file, then it can express this to the packaging system by putting "logrotate" in its Depends: field... SRH -- Steve Haslam http://www.arise.demon.co.uk/ [EMAIL PROTECTED] Debian GNU/Linux Maintainer [EMAIL PROTECTED] but I won't admit to needing you I'll never say that's true, not to you [sister machine gun]
pgp4i2fgvGhse.pgp
Description: PGP signature
