Direct or indirect libdependencies (using the case)

Peter Jeremy peter at
Thu Jun 3 12:37:32 UTC 2010

On 2010-Jun-01 10:54:02 +0200, Jan Henrik Sylvester <me at> wrote:
>Yesterday, I was chasing, rebuilding all ports that got 
>bumped, checking with libchk for other dependencies, and 
>forcing a rebuild of all these packages: All but two of them had an 
>indirect dependency on devel/gettext (and I did email the maintainers of 
>devel/ccrtp and textproc/gsed linking without a dependency).

This might be unrealistic but, IMHO, these "indirect dependencies" should
not exist.  IMHO, there should only be two situations:

1) Port X directly links against or dlopen's from port Y.

In this case, port Y should be listed in LIB_DEPENDS or equivalent
for port X and port X will need a portrevision bump and rebuild if
the port Y ABI changes (eg a .so version bump)

2) Port X directly links against or dlopen's and pulls
   in from port Y.

In this case, port X should not be directly accessing any symbols in  If the ABI changes, will need to be rebuilt
but unless the ABI changes, there should be no need to rebuild
port X.

Are there any other situations that have to be considered?

Peter Jeremy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
Url :

More information about the freebsd-ports mailing list