Date: Fri, 17 Feb 2012 14:36:49 +0000 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: Alex Dupre <ale@FreeBSD.org> Cc: freebsd-ports@FreeBSD.org Subject: Re: recent portrevision bump for libvpx Message-ID: <4F3E6601.9000405@infracaninophile.co.uk> In-Reply-To: <4F3E507C.9080008@FreeBSD.org> References: <4F3E289D.9050605@FreeBSD.org> <4F3E2CED.90601@FreeBSD.org> <4F3E2E08.40007@FreeBSD.org> <4F3E451E.5070001@infracaninophile.co.uk> <4F3E507C.9080008@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigB76E497C509C46F1C474165F
Content-Type: text/plain; charset=x-viet-vps
Content-Transfer-Encoding: quoted-printable
On 17/02/2012 13:05, Alex Dupre wrote:
> Matthew Seaman wrote:
>> Adding code to run ldd(1)
>> against the files installed by the port and processing the results
>> shouldn't be too hard.
>=20
> This could be an idea for ports maintainers, to verify if LIB_DEPENDS i=
s
> set correctly, but cannot be used as its generic replacement.
Quite so, but that's not the principal benefit. It's a way of
efficiently answering the question "which of my installed ports need to
be re-built as a result of this shlib change?" For the end users
primarily. Having this data recorded in /var/db/pkg/foo-9.99/+CONTENTS
makes answering that question something like:
grep -l '@comment SHLIB:libwhatever' /var/db/pkg/*/+CONTENTS | \
cut -d '/' -f 5
Ideally a ports management tool would notice if any port updated a shlib
to a different ABI version and suggest to the user which ports to rebuild=
=2E
I assume something similar could be done for the new pkg tools, but I
really have no idea how hard that would be.
Cheers,
Matthew
--=20
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
JID: matthew@infracaninophile.co.uk Kent, CT11 9PW
--------------enigB76E497C509C46F1C474165F
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.16 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk8+ZgkACgkQ8Mjk52CukIzuMwCgh3ziRQ8E8tz+mWVkY4IEih/M
l5wAnAvf4CaaluSNeOQFAlufplEGPJ3K
=6XSr
-----END PGP SIGNATURE-----
--------------enigB76E497C509C46F1C474165F--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F3E6601.9000405>