dependency detail
Ryan Schmidt
ryandesign at macports.org
Mon Dec 2 15:23:53 PST 2013
On Dec 2, 2013, at 08:24, Peter Danecek <Peter.Danecek at bo.ingv.it> wrote:
> This is a short one. I would have a dependency which is needed at activation. So I assume it does not qualify as build dependency, in fact it is not needed to create the binary package.
>
> Now, I wonder if run dependency is appropriate. At least if understanding correctly terminology, "run time" dependencies might become available only **after** installation. I think, in practice this is not the case, but should I rely on this?
This sounds like a runtime dependency to me.
If you run “sudo port install foo”, then all of its dependencies will be installed before foo is installed.
However, if you run “sudo port build foo”, then build and library dependencies will be installed first, but runtime dependencies won’t be.
More information about the macports-dev
mailing list