Date: Fri, 10 Jun 2022 21:50:06 +0900 From: Tomoaki AOKI <junchoon@dec.sakura.ne.jp> To: ports@freebsd.org Cc: jbo@insane.engineer Subject: Re: Difference between LIB_DEPENDS and RUN_DEPENDS Message-ID: <20220610215006.531a56a42178103bebf03b74@dec.sakura.ne.jp> In-Reply-To: <ATW5B6XJvLk8DwLIVd5VKijiewdSl4nCjaUl1t0yQXSd-UNGePK4PAJ5LP4RvvYnkscdha0QgyIYEd4hinx1k6oLkL99lJKgk40XkYSU1og=@insane.engineer> References: <ATW5B6XJvLk8DwLIVd5VKijiewdSl4nCjaUl1t0yQXSd-UNGePK4PAJ5LP4RvvYnkscdha0QgyIYEd4hinx1k6oLkL99lJKgk40XkYSU1og=@insane.engineer>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 10 Jun 2022 12:03:16 +0000
jbo@insane.engineer wrote:
> Hello folks,
>
> Maybe an unusual request but could somebody elaborate on the difference between LIB_DEPENDS and RUN_DEPENDS?
> I read the corresponding handbook section thrice and it's not clear to me when to use which - I must be missing something obvious.
>
> RUN_DEPENDS appears to be for runtime dependencies. But when do I want to use LIB_DEPENDS?
> I'm working on a port of a C++ library which depends on on some shared libraries (provided by existing ports) but it's not clear to me whether those should be listed in RUN_DEPENDS or LIB_DEPENDS.
>
> Best regards,
> ~ joel
My guess is that...
LIB_DEPENDS: Include something dynamically linked (by rtld) on runtime.
RUN_DEPENDS: Include something called by fork*() or exec*() as
independent process, excluding LIB_DEPENDS.
In ancient days before USE_* or USES=* were introduced, IIRC, something
like perl, python, ruby or bash was RUN_DEPENDS.
--
Tomoaki AOKI <junchoon@dec.sakura.ne.jp>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20220610215006.531a56a42178103bebf03b74>