Opened 7 years ago
Closed 7 years ago
#54749 closed defect (fixed)
gpgme 1.9.0_1: Bad dependency on gnupg21
Reported by: | jdswinbank (John Swinbank) | Owned by: | lbschenkel (Leonardo Brondani Schenkel) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | lbschenkel (Leonardo Brondani Schenkel), dbevans (David B. Evans), tgyurci (Teubel György) | |
Port: | gpgme |
Description
As of #51650, gnupg21 provides ${prefix}/bin/gpg
(not gpg2
). This breaks the gpgme dependency on path:bin/gpg2:gnupg2
.
Change History (4)
comment:1 Changed 7 years ago by lbschenkel (Leonardo Brondani Schenkel)
comment:2 Changed 7 years ago by lbschenkel (Leonardo Brondani Schenkel)
I have submitted a tentative fix implementing my proposal above on https://github.com/macports/macports-ports/pull/743 for review/discussion.
comment:3 Changed 7 years ago by tgyurci (Teubel György)
Cc: | tgyurci added |
---|
comment:4 Changed 7 years ago by lbschenkel (Leonardo Brondani Schenkel)
Owner: | set to lbschenkel |
---|---|
Resolution: | → fixed |
Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
@dbevans: it seems that the current gpg situation became a little bit messy:
gnupg
installs onbin/gpg
gnupg2
installs onbin/gpg2
gnupg21
installs onbin/gpg
and conflicts with gpg1 and gpg2I think that it's probably worth it to open a discussion on the mailing list about how to handle the various GnuPG versions moving forward -- including 2.2 that was just released.
Regarding GPGME, for now I suggest that we introduce a
gnupg20
variant which is activated by default and has the current dependency, so no change for existing users. Users using 2.1.x need to select thegnupg21
variant instead that will have a hard dependency ongnupg21
(we cannot rely onpath:bin/gpg
anymore since it could be satisfied by GnuPG 1.x), giving them an immediate solution. Then we can decide later when it is appropriate to switch defaults. How does that sound?