On Nov 10, 2013, at 7:23 AM, Michael Dickens <michae...@macports.org> wrote:
> How does one indicate a runtime dependency that is checked for at > configure time and not used for building or linking? As previously stated, one could use either depends_lib or depends_build + depends_run, because depends_lib does not currently mean anything other than "required at both build time and run time". > I've been using depends_run, but I'm not sure that always works because of the > configuration checking. Are these dependencies installed before configuration > of the target port? This is incorrect because there is no guarantee that the dependency will be present during the configure phase. Running "port configure foo" will not trigger installation of foo's runtime dependencies. It's easy to miss this if you always have the dependencies installed, or if you test with "port install foo", which (I believe) installs all dependencies before starting on foo. vq _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
