#52368 closed enhancement (fixed)
gpgme @1.7 allow installing with gnupg21
| Reported by: | lbschenkel (Leonardo Brondani Schenkel) | Owned by: | dbevans (David B. Evans) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.3.4 |
| Keywords: | Cc: | ||
| Port: | gpgme |
Description
The current port has a dependency on gnupg2, which prevents it from being used with gnupg21 even though that is supported by gpgme. I have attached a diff that changes the dependency to the gpg2 binary instead, so either gnupg2 or gnupg21 will satisfy it. gpg2 was left as the default dependency in case gpg2 is not available.
Patch is attached.
Attachments (1)
Change History (6)
Changed 8 years ago by lbschenkel (Leonardo Brondani Schenkel)
| Attachment: | gpgme.diff added |
|---|
comment:1 Changed 8 years ago by neverpanic (Clemens Lang)
| Cc: | devans removed |
|---|---|
| Owner: | changed from macports-tickets@… to devans@… |
comment:3 Changed 8 years ago by dbevans (David B. Evans)
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Enhancement committed in r153149. gpgme now expresses it dependencies on gnupg as path depspecs which can be satisified by either gnupg2 (the default) or gnupg21. Since gnupg21 uses a new key storage format that cannot be easily reverted, gnupg21 should be used with caution.
comment:4 follow-up: 5 Changed 8 years ago by lbschenkel (Leonardo Brondani Schenkel)
Thanks. Was the fact that revision was not bumped deliberate or an oversight?
comment:5 Changed 8 years ago by dbevans (David B. Evans)
Replying to leonardo.schenkel@…:
Thanks. Was the fact that
revisionwas not bumped deliberate or an oversight?
Deliberate. The contents of gpgme has not changed, only the version of gnupg installed. The code configures at run time looking for ${prefix}/bin/gpg2. Whichever version is installed will be used.
The Cc field expects email addresses, not user names.