On Wed, 10 May 2006 09:04:14 -0400, James Vega <[EMAIL PROTECTED]> said:
> On Wed, May 10, 2006 at 12:32:53AM -0400, Hubert Chan wrote: >> Hmm... alsaplayer-common Depends: on "alsaplayer-alsa | >> alsaplayer-output" and "alsaplayer-gtk | alsaplayer-interface". Is >> this really a problem? My question, which I guess wasn't clear, was whether the circular dependency is still a problem if one of the dependencies in the cycle is an or'ed dependency. [...] > There's no real reason that alsaplayer-common needs to Depend on an > alsaplayer-output variant or an alsaplayer-interface variant. As a > user, if I just want to look at the common files for some reason, I > sholudn't need to install alsaplayer-(output|gtk). Those would be > fine as Recommends. alsaplayer-common contains the main alsaplayer binary (/usr/bin/alsaplayer), which does not function without an alsaplayer-output and alsaplayer-input plugin. So yes, it really does depend on these. (I would have named alsaplayer-common something different -- maybe alsaplayer-bin, or just alsaplayer, but that was what it was called when I inherited it.) A Recommends: might work, since aptitude will try to install recommended packages, but I think that Depends: describes the package relationship much better, and so I don't want to change it unless absolutely necessary. -- Hubert Chan - email & Jabber: [EMAIL PROTECTED] - http://www.uhoreg.ca/ PGP/GnuPG key: 1024D/124B61FA (Key available at wwwkeys.pgp.net) Fingerprint: 96C5 012F 5F74 A5F7 1FF7 5291 AF29 C719 124B 61FA -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]