gnupg is a big meta package pulling in all sorts of weird stuff
people don't want by default on their machine, like a wks server.

That wks server in experimental now pulls in a mail transport
agent.

Hence installing gpg for example pulls in gnupg by Recommends,
and then the wks server and then the mail transport agent. Ugh.

It stands to reason that gnupg2 should have:

1. gnupg should move to the metapackages section
2. All Recommends on gnupg should be removed, we don't want that
   installed by default.
3. gpg should Recommends keyboxd and dirmngr as they will frequently be
   needed when using gpg

And then we should clean up all reverse dependencies to say gpg.

I think I plan to do this in Ubuntu. The alternative would be
to demote all non-interesting gnupg dependencies to suggests,
those would be:

- gnupg-utils
- gpg-wks-server
- gpgv [stuff will depend on that anyway if it needs it, like apt does]
- maybe gpg-wks-client

This may make the gnupg package *actually useful* rather than
be a pointless metapackage that nobody actually wants to install.

Let me know what you think but this surely is a mess
we need to sort out, and I have about ~ next week to
do so downstream.

Control: tag -1 patch

Implemented in
https://salsa.debian.org/debian/gnupg2/-/merge_requests/13

as just uploaded to Ubuntu.

Also note MR 14, which fixes the autopkgtests for 2.4.

My intention is to also change other packages' Depends and Recommends on
gnupg to generally say gpg instead, but not in the next weeks, but like
after Ubuntu has import stop as I don't want to do that in 24.04 cycle.

Hi Julian--

I agree with this generally, but upstream seems to generally want all
packages available in a standard installation, and hasn't committed to
clear boundaries about what things will fail when certain subpieces are
missing.  See for example discussion in #873499

The explicit Recommends is trying to encourage behavior that aligns with
upstream's wishes.

Andreas resolved this by moving gpg-wks-server to a Suggests from a
Recommends.

This is a good idea, i've moved it there in git, and it should be
included in the next upload.

I'm reluctant to do these parts for the above reasons.
Andreas!)

I'm moving the remaining three packages from the above list to
Recommends: (instead of Depends:) for the gnupg package.

I don't know how to strike a happy balance between what most users want
(something minimal, to not have to think about OpenPGP at all, and have
it just work silently in the background) and what upstream seems to want
(a complicated interconnected system with lots of subtle
configurability).