Hiya, On Sun, Jan 03, 2010 at 10:06:11PM -0200, Marco Túlio Gontijo e Silva wrote:
Hi Iain. [...] Quoting policy:Depends(...) The Depends field should be used if the depended-on package is required for the depending package to provide a significant amount of functionality.My point is: is there even an unusual case in that it could be useful to have cabal-install installed and not ghc6?
Maybe to use a locally installed ghc in /opt or similar. I don't know...
By the way, this quote made me remind of the discussion about -doc packages relationship. I can think of unusual cases in which one would want to install a -doc package with broken links, to avoid having to install all the -doc stack, for instance, when a user wants just to check the doc of a specific package and remove the package some minutes latter. So, reading this quote, I think Recommends is the way to go for -doc packages.
Given that recommends are installed by default, a user would have to specifically request (or accept an aptitude suggestion in the case of conflicts) this situation. This gives a decent OOTB experience while still affording flexibility to power users. I don't even remember if I commented on that discussion, but Recommends seems correct to me, for both -doc and cabal-install.
Description: Digital signature