On Tue, Aug 29 2017, Sean Whitton wrote: >> binary itself. To avoid extra dependencies, it would be nice to update >> the dependency to "gnupg | gnupg2 | gpg". > > Well, gnupg2 is a transitional package, so no point in having that. > > Would 'gpg' be enough? The package description says it can't do > anything with secret keys, which would render git-remote-gcrypt pretty > much useless.
I currently have an equivs package that provides gnupg2 while depending only on gpg to satisfy existing packages, and had no problems. I'm not sure what the description intends about "secret keys", since I can generate and manipulate secret keys as usual. gnupg just depends on additional modules by default. If you need specific functionality, such as dirmngr, I'd say you should depend on it explicitly (look at python-apt), but avoid to depend on the full suite. I never ever used gpgsm for example, and with gpg 2.1.23 I even disabled dirmngr.
