Quoting Jonathan Dowland (2018-10-23 11:06:15) > On Mon, Oct 22, 2018 at 11:32:21AM -0400, Marvin Renich wrote: > >I'm going to use the neomutt → libgpgme → gnupg as an example, but > >this applies as well to any other case where someone has a legitimate > >use for installing one package without a dependency that would > >normally be found with that package. > > > >If libgpgme Depends: gnupg, then anyone who wishes to install > >libgpgme (or, in cases like this, a package that has a Depends: > >libgpgme) without gnupg must either use equivs to build a fake gnupg > >package or build a modified libgpgme package that does not depend on > >gnupg. > > Both of Depends and Recommends in this case have drawbacks. It's a > matter of weighing them up and considering their likelyhoods on a case > by case basis. In this case, the maintainer must weigh the experience > of users who may install mutt without gnupg and get a compromised > experience, and how likely they are to hit that, versus the likelyhood > that a user would be significantly troubled by installing gnupg even > if they don't intend to use it; and in the latter case, factor in that > we do have a system for addressing that, equivs, as you point out.
I believe you are mistaken: What should be weighed on a case-by-case basis is Recommends versus Suggests. Depends should *only* be used when not even exotic use is possible without the package relation satisfied. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: signature
