How to stay with GnuPG 2.0.x (security/gnupg20)

Kevin Oberman rkoberman at gmail.com
Fri Nov 21 01:47:29 UTC 2014


On Thu, Nov 20, 2014 at 9:26 AM, Dr. Peter Voigt <pvoigt at uos.de> wrote:

> On Thu, 20 Nov 2014 14:40:21 +0100
> "Dr. Peter Voigt" <pvoigt at uos.de> wrote:
>
> > I am on 10.1-RELEASE (amd64) and I am currently using GnuPG 2.0.26:
> >
> > # pkg version |grep gnupg
> > gnupg-2.0.26_1                     <
> >
> > However, GnuPG 2.1 is offered as an update:
> >
> > # pkg version -vIL=
> > gnupg-2.0.26_1                     <   needs updating (index has
> > 2.1.0)
> >
> > Inspecting the ports tree show that there are two different ports:
> > security/gnupg20 and security/gnupg.
> >
> > How can I stay with security/gnupg20? Portmaster/pkg currently forces
> > me to upgrade. Is there a switch in /etc/make.conf?
> >
> > Regards,
> > Peter
>
> Well, found out that it is obviously a matter of changing a ports
> origin:
>
> # pkg set -o security/gnupg:security/gnupg20
>
> Now portmaster/pkg do no longer "force" me to upgrade to version 2.1.
>
> I hope this is the right way to do, I am still too unexperienced with
> ports processing.
>
> Regards,
> Peter
>

Yes, that is one way to do it.  Both portmaster and portupgrade also have a
'-o' option that is used similarly. (E.g. portmaster -o security/gnupg20
security/gnupgp) Note the order of the arguments and that the delimiter is
a space instead of a ':'.
--
R. Kevin Oberman, Network Engineer, Retired
E-mail: rkoberman at gmail.com


More information about the freebsd-ports mailing list