Thanks, Guy, for clarifying that issue. I've added the following to the programmers' manual: > When selecting which level of dependency to use you should consider > how important the depended-on package is to the functionality of the > one declaring the dependency. Some packages are composed of > components of varying degrees of importance. Such a package should > list using <tt/Depends/ the package(s) which are required by the more > important components. The other components' requirements may be > mentioned as Suggestions or Recommendations, as appropriate to the > components' relative importance.
Ian.
