On Tue, Jun 06, 2006 at 11:59:39AM +0200, Peter Eisentraut wrote: > Does anyone want to put in a vote on which way to break the dependency loop? > Basically, there are two ways to go about it:
> ntp-server Depends ntp-simple | ntp-refclock > ntp-simple Recommends ntp-server > ntp-refclock Recommends ntp-server > Two, > ntp-server Recommends ntp-simple | ntp-refclock > ntp-simple Depends ntp-server > ntp-refclock Depends ntp-refclock > The first treats ntp-server as the well-known public package to install and > the other two as implementation variants. This is a bit like the kaffe > package, say. > The second treats ntp-server as a sort of ntp-common package that gets pulled > in by either package you install. > The first seems to be a bit more user-friendly, because "apt-get install > ntp-server" will do something reasonable. It also seems to have been the > original intent, seeing that the user management is in the ntp-simple and > ntp-refclock packages, which would seem to indicate that they were intended > to be configured first. Note that the behavior that triggered this bug report already implies a preferred solution: with the current package set, there is one package that has to be configured before the other due to the user creation. If in doubt, that's the dependency I would suggest respecting. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
