On Wed, Apr 23, 2014 at 9:58 AM, Tom Furie <t...@furie.org.uk> wrote: > The intention of the package relationships was supposed to be - > > Depends: This package won't run unless you have this other package > installed. > > Recommends: This package will run without this other package, but > possibly with reduced functionality. > > Suggests: This package will run fine without this other package, but the > other package would be nice to have along with this. > > This seems to have been lost somewhere along the way.
Those concepts are fine for concrete packages. My MUD client Gypsum, if I were to package it as a .deb, would Depend on Pike and GTK, would Recommend the latest Pike (if it's possible to depend on one version and recommend another), and probably wouldn't have any Suggests. But with meta-packages, how does that work? "Standard graphical desktop" definitely requires some things (like a desktop environment, obviously), but what about all those pre-installed programs? Are they Recommends or Suggests? ChrisA -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAPTjJmqAwzSyOSy4ku_uRz=yucfrhldtu0soysw-cabnr1a...@mail.gmail.com
