On Thu, Jun 08, 2006 at 08:17:53PM +0200, Peter Eisentraut wrote: [time-daemon] > > > What would be the operational benefit from having such a > > > pseudopackage? > > It's recommended by policy; > > /usr/share/doc/debian-policy/virtual-package-names-list.txt.gz > That is not an operational reason. The virtual package name list does > not specify the precise interfaces that a virtual package providing > package needs to offer, so by itself it's useless as a guideline.
I've got one and I got mildly annoyed that this was not solved for ntp yet. I just got a bugreport against my package which wants chrony to be added to the `ntpdate | ntp' dependency of it. An accurate time is needed for aiccu just like for Kerberos because it is included in the handshake with the tunnel broker which will deny the IPv6 tunnel request if the time is too far off (IIRC > 300s). Thus I need to depend on some sort of time daemon, but only chrony and openntpd provide time-daemon, ntp does not, which will force me to the silly `ntpdate | ntp | time-daemon' dependency. Currently chrony and openntpd block installation of ntp manually via a seperate conflicts, instead of just conflicting against time-daemon. Kind regards, Philipp Kern
signature.asc
Description: Digital signature
