BUG: Repair bad dependency entries in GNOME ports

[rhwood@…]

Almost every single GNOME port has bad dependency lists in it.

These ports all need to be built on a clean machine with the trace (-t) option set and have the portfiles modified accordingly.

Priority for this should be with the ports in the gnome-platform-suite, then the gnome-desktop-suite, and finally in the gnome-bindings-* ports.

At one point, a number of the GNOME ports had their dependency structures simplified, so that if a dependency chain A->B->C->D existed, port A was set to depend only on port B, and not on ports C and D. While this made port management simple, it means that a port does not depend on every port that it links against, which, in certain circumstances is a significant problem.

[nox@…]

This does not only concern GNOME, subversion is affected too:

% otool -L $(which svn)
/opt/local/bin/svn:
<snip>
        /opt/local/lib/libssl.0.9.8.dylib (compatibility version 0.9.8, current version 0.9.8)
        /opt/local/lib/libcrypto.0.9.8.dylib (compatibility version 0.9.8, current version 0.9.8)
<snip>

but subversion does not depend on openssl, neon does.

[rhwood@…]

Reassign to self since I own most of these ports.

This activity is ongoing, but it is unstructured and occurring only as a port gets upgraded.

[rhwood@…]

Gui_dos has the GNOME ports well in hand, without this task, so I'm closing it.

[(none)]

Milestone Port Bugs deleted