Date: Tue, 16 Dec 2014 06:07:47 -0800 From: David Wolfskill <david@catwhisker.org> To: freebsd-ports@freebsd.org Subject: emulators/pipelight, BUILD_DEPENDS, and gpg2 Message-ID: <20141216140747.GR1115@albert.catwhisker.org>
next in thread | raw e-mail | index | archive | help
--6nfUOKxk8V1TQsEu
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On my laptop, I try to keep things fairly up-to-date: I perform source
updates daily on stable/10, and then update the installed ports (using
portmaster); I keep a local private mirror of the FreeBSD SVN repo
(which I update automagically overnight) locally on the laptop.
Back on 20 Nov, one of the ports that was updated was security/gnupg --
updating that port from gnupg-2.0 to -2.1. I then discovered
(empirically) that gnupg-2.1 would not decrypt some rather important
information that I had stored, though at the time, I didn't know what
caused this (and I wasn't expecting such a silent POLA-contravening
change merely from a revision number bump).
After a bit of flailing about (on my part), I found that:
portmaster -o security/gnupg20 gnupg-2.1\*
(thus forcing a reversion to gnupg-2.0) resolved the problem in a way
that preserved my access to the information in question.
This morning, one of the ports for which an update was attempted was
emulators/pipelight:
=3D=3D=3D>>> The following actions will be taken if you choose to proceed:
=2E..
Upgrade pipelight-0.2.7.3_5 to pipelight-0.2.7.3_6
Install security/gnupg
Now, I plead "guilty as charged" to failing to note the stated intent to
try to "Install security/gnupg". (That attempt failed, by the way:
=2E..
=3D=3D=3D> Installing for gnupg-2.1.0_1
=3D=3D=3D> Registering installation for gnupg-2.1.0_1 as automatic
Installing gnupg-2.1.0_1...
pkg-static: gnupg-2.1.0_1 conflicts with gnupg20-2.0.26_2 (installs files i=
nto the same place). Problematic file: /usr/local/bin/gpg-agent
=2E...
But that's not the focus of this note.)
Apparently "gpg2 is a BUILD_DEPENDS for emulators/pipelight:
# Created by: Kris Moore <kmoore@FreeBSD.org>
# $FreeBSD: head/emulators/pipelight/Makefile 374755 2014-12-15 17:00:22Z k=
moore $
PORTNAME=3D pipelight
DISTVERSION=3D 0.2.7.3
PORTREVISION=3D 6
CATEGORIES=3D emulators
=2E..
BUILD_DEPENDS=3D ${LOCALBASE}/bin/gpg2:${PORTSDIR}/security/gnupg \
${LOCALBASE}/bin/bash:${PORTSDIR}/shells/bash
LIB_DEPENDS=3D libxml2.so:${PORTSDIR}/textproc/libxml2
=2E...
And I have "gpg2" available:
g1-253(11.0-C)[19] ls -lToi `which gpg2`
16133409 -r-xr-xr-x 1 root wheel - 652956 Nov 22 05:00:32 2014 /usr/loca=
l/bin/gpg2
But I have it from security/gnupg20:
g1-253(11.0-C)[23] pkg-static which `which gpg2`
pkg-static: Warning: Major OS version upgrade detected. Running "pkg-stati=
c install -f pkg" recommended
/usr/local/bin/gpg2 was installed by package gnupg20-2.0.26_2
Is there, perhaps, a way to construct the BUILD_DEPENDS for pipelight
so that it can use gpg2 from ... well, wherever it was installed
=66rom, and revert to bringing in a new port only if gpg2 isn't
already available?
[PS: Don't let the above-quoted whines about "Major OS version
upgrade detected..." distract you: I had attempted the emulators/pipelight
update under stable/10, as described above. At the time of this
writing, I had flipped the laptop to boot from a different slice,
where I am performing my daily update of head.]
Peace,
david
--=20
David H. Wolfskill david@catwhisker.org
Actions have consequences ... as do inactions.
See http://www.catwhisker.org/~david/publickey.gpg for my public key.
--6nfUOKxk8V1TQsEu
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQJ8BAEBCgBmBQJUkDyzXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ4RThEMDY4QTIxMjc1MDZFRDIzODYzRTc4
QTY3RjlDOERFRjQxOTNCAAoJEIpn+cje9Bk72RMP/2Iya2Tj4KJoDAO9IfStQ6Fi
GbDaZ0oNzxyOMtxbkPm6In0dixGRzwbc/oKQn1/MfNMmwFniPA+O2xV8KC1UEyt4
uik+ln5RHU2CLtXlRKTA61vU4FD2ipg5ANQEIAnMzAYetRzRDdcg6vjiezREp9Jr
hKiJf5qbW/AmEsvFHVbWIssZRYdNVDorsbcJdmYtmkJh2wl4CbxT7hRHci5NhZGj
ZPoP6JKOAYaSgggttFWoKDFSjj4vUidv9Vv+FX2hLX7rfTe7aj0Zxc1m6/kxuEmT
3xx9bgxC31yjj8F5UZvm54bV64NnsUtMnDdHVxcFhY1dSg8UQ3vXmCmuvGOEPhxK
WIoYf3X/SengLgmJTk+2gPdIKFYjLgjfxnhGtH57zlsrenqk7x8dHzLYg1WBbazd
gtmiTYe6ZQRWI2HylpxjugIptbcPDNKiFyH+u/j3yhH/BhfBPl+PYAX6Vq+ff588
E/z6t+uUuQ5Hlk39v1ceCzD4Uey4/1irAx2k6643DCoELR680i4AMUd/E2idRtJk
muYZLF25moEi3Ji4JIc6OoCkRzC50SaQv17AeIL8gb/tCND09dPRvfO3ESmqI1/g
tsuYLYDIjqbGVMWZYj4FoEjE5hmCYOQ4+TNpJ76PepZcxHsm9Zso5egbMDXluK4t
nrvtYRXN2g8/pSxDPsfC
=RtMG
-----END PGP SIGNATURE-----
--6nfUOKxk8V1TQsEu--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20141216140747.GR1115>