On Mon, Mar 3, 2008 at 1:24 AM, Jeremy Huddleston <jeremyhu@berkeley.edu> wrote:
I'd prefer to use the system provided libraries if they're available and of sufficient version. If the library isn't found, you can certainly pull it in yourself, but the library *should* be available (why would it not be).
So you'd be happying with dependencies of the form lib:libXt:xorg-libXt etc... then the dependencies would be satisfied by the system versions on Leopard and then on Tiger the xorg-libXt port would be built. There's one problem I see with this, which is the reason why MacPorts uses its own libraries in the first place. When Leopard+1 is released it will no doubt include a more recent xorg than Leopard and if a given port requires a more up to date version of the given xorg package that is available in Leopard then problems could ensue.
One of my biggest hang-ups dealing with MacPorts has been needing to sanitize my C_INCLUDE_PATH, etc to remove macports because the protos installed in /opt/local were too old to build the server. Plus, I've had some trouble tracking down problems because of which version of fontconfig was being used by an executable, etc. It just makes life a lot simpler for both of us if we don't doubly install things.
Thanks for your input, I have a think and start a discussion regarding this on the MacPorts dev list. Cheers Adam