On 17/02/2012 10:38, Alex Dupre wrote: > Alex Dupre wrote: >> Ideally a port should include in LIB_DEPENDS all the direct dependencies. > > And consequentially it should be bumped *only if* a direct dependency > has a library version bump. With the current "link to all" attitude, we > are never sure what need to be bumped, because of hidden dependencies, > and so "portmaster -r" and similar approaches are always recommended in > addition to probabilistic portrevision bumps. >
You could record all the shared libraries used by a port as comments in the +CONTENTS list when it is packaged. Adding code to run ldd(1) against the files installed by the port and processing the results shouldn't be too hard. Then portmaster(8) et al could have a way of telling precisely what needed to be rebuilt for this sort of shlib version bump. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW
signature.asc
Description: OpenPGP digital signature