If I understand correctly, the problem for this pull request is that GPGME is being run when the gnupg recipe is run, as part of the tests when it builds gnupg (this might be new on their part as of 2.2.17?), and GPGME requires QT, so the gnupg recipe is now breaking if you don’t have QT installed, because it includes GPGME in its tests and GPGME won’t build without QT.
So, this isn’t a problem, really, with GPGME, I think. If GPGME depends on gnupg, and we make it so gnupg installs ok, then that will work just fine when you try to separately install GPGME. The problem here looks to me like it is that tests for gnupg 2.2.17 include GPGME, which depends on QT, and so the install of gnupg is failing, while GPGME is trying to install its dependencies.
To fix this, if we just want the base gpg install to not test on GPGME, you’d need to know if there is a configure flag for gnupg to tell it to skip GPGME tests. If this exists, we could just set this flag in gnupg.rb and be done.
If that doesn’t exist, I guess you could go to the gnupg people and see if they would add one in. It would depend on how they have implemented their tests.
If there is no option in the base gnupg install to skip those GPGME tests, then, to just install gnupg, you are down to skipping all tests, requiring QT, or perhaps some other options I don’t know about because I am new to all this.
Make sense? Am I confused or missing something?
I’ll try to look into the configure options for gnupg later today, see if the option to skip GPGME tests (and so avoid needing QT for gnupg) is implemented.