Don Armstrong <d...@debian.org> writes: > Graceful breakage isn't what policy requires; it's whether the package > is a requirement for a significant[1] amount of functionality. [That > said, specifically indicating that a Recommends: or Suggests: package is > required to use certain optional functionality in documentation or in > the actual program output is always a plus.]
The general rule of thumb that I've personally tried to follow is to mention in the package long description the reason for any Recommends or Suggests. That seems like the best place for users to see that information while installing the package. (I try to also mention it in README.Debian as well.) -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/874nnlmkyq....@windlord.stanford.edu
