Am 01.04.2008 um 11:02 schrieb Jordan K. Hubbard:
This is sadly somewhat controversial. I think dependencies should definitely be directed at the depot location, e.g. something that links with, say, jpeg version 6.2, shouldn't link to /usr/lib/ libjpeg.62.dylib but rather /opt/local/var/macports/software/jpeg/ 6b_2/opt/local/lib/libjpeg.62.dylib, and so on and so forth for any absolute-path dependencies. Then whether something is "active" or not has nothing to do with whether it can be depended on. Every time the subject comes up, however, various people rapidly get the creeping crawlies and we lose the courage to actually attempt this.
Hm, do you suggest using and linking only to ports? I find the lib:* dependency quite useful as I'm using the official .dmg package of MySQL from the MySQL homepage instead of the mac port (mainly because I've already been using it before installing MacPorts). Allowing such dependencies offers end users more choice in what software "distribution" to use, as long as libraries are correct.
Sorry if I misunderstood you, just wanted to point out that dependencies against non-ports software can make sense for some people ;-)
Robert _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-dev
