#51650: gnupg21 @2.1.12_0: install symlinks for "gpg" and "gpgv" --------------------------+---------------------- Reporter: larryv@… | Owner: jann@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.99 Resolution: | Keywords: haspatch Port: gnupg21 | --------------------------+---------------------- Comment (by jann@…): The reason why gpg 2.* is not installed as gpg is that you can install it alongside gpg 1.* . This may be less relevant now though. -- Ticket URL: <https://trac.macports.org/ticket/51650#comment:1> MacPorts <https://www.macports.org/> Ports system for OS X

#51650: gnupg21 @2.1.12_0: install symlinks for "gpg" and "gpgv" --------------------------+---------------------- Reporter: larryv@… | Owner: jann@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.99 Resolution: | Keywords: haspatch Port: gnupg21 | --------------------------+---------------------- Comment (by jann@…): No sym link is required if we want this. There is a configure switch to install the binary as just gpg. I would keep everything as is though. Changing it will just break things. -- Ticket URL: <https://trac.macports.org/ticket/51650#comment:3> MacPorts <https://www.macports.org/> Ports system for OS X

#51650: gnupg21 @2.1.12_0: install symlinks for "gpg" and "gpgv" --------------------------+---------------------- Reporter: larryv@… | Owner: jann@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.99 Resolution: | Keywords: haspatch Port: gnupg21 | --------------------------+---------------------- Comment (by larryv@…): Replying to [comment:2 ionic@…]:

We can't do this in `gnupg2` because users can have both `gnupg` and `gnupg2` installed, though, so the behavior of the `gpg` and `gpgv` binaries will be unreproducible without knowing the system state first. Not sure we want that, larry?

I hadn’t considered that. I wouldn’t call that state of affairs //unreproducible// (`gnupg` and `gnupg21` would always install `gpg` and `gnupg2` would never do so), but it certainly could be confusing. It’s easy for someone to understand why 1.//x// installs `gpg` and 2.//x// installs `gpg2`; it would be harder to understand why 1.//x// and 2.1.//x// installed `gpg` but 2.0.//x// did not. I’d understand if you wanted to close this at wontfix. (My personal motivation is getting `keybase` working with something that isn’t `gnupg`, but perhaps it’d be better to patch that instead of this.) -- Ticket URL: <https://trac.macports.org/ticket/51650#comment:5> MacPorts <https://www.macports.org/> Ports system for OS X

#51650: gnupg21 @2.1.12_0: install symlinks for "gpg" and "gpgv" --------------------------+---------------------- Reporter: larryv@… | Owner: jann@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.99 Resolution: | Keywords: haspatch Port: gnupg21 | --------------------------+---------------------- Comment (by larryv@…): The Keybase software itself can find “gpg2” (and actually [https://github.com/keybase/client/blob/v1.0.16/go/libkb/gpg_cli.go#L54 prefers it]), but our `keybase` port currently has a `bin:gpg:gnupg` dependency. -- Ticket URL: <https://trac.macports.org/ticket/51650#comment:7> MacPorts <https://www.macports.org/> Ports system for OS X