From nobody Fri Jun 10 12:50:06 2022 X-Original-To: ports@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id AE7D3859314 for ; Fri, 10 Jun 2022 12:50:17 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from www121.sakura.ne.jp (www121.sakura.ne.jp [153.125.133.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4LKLQw2MWhz4gVF for ; Fri, 10 Jun 2022 12:50:15 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from kalamity.joker.local (123-1-85-147.area1b.commufa.jp [123.1.85.147]) (authenticated bits=0) by www121.sakura.ne.jp (8.16.1/8.16.1/[SAKURA-WEB]/20201212) with ESMTPA id 25ACo6ZH040608; Fri, 10 Jun 2022 21:50:06 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) Date: Fri, 10 Jun 2022 21:50:06 +0900 From: Tomoaki AOKI 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: References: Organization: Junchoon corps X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd13.0) List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4LKLQw2MWhz4gVF X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of junchoon@dec.sakura.ne.jp has no SPF policy when checking 153.125.133.21) smtp.mailfrom=junchoon@dec.sakura.ne.jp X-Spamd-Result: default: False [-1.22 / 15.00]; RCVD_TLS_LAST(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; MV_CASE(0.50)[]; NEURAL_HAM_LONG(-0.66)[-0.661]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[sakura.ne.jp]; AUTH_NA(1.00)[]; HAS_ORG_HEADER(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-0.99)[-0.986]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_MEDIUM(-0.97)[-0.972]; MLMMJ_DEST(0.00)[ports]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7684, ipnet:153.125.128.0/18, country:JP]; RCVD_COUNT_TWO(0.00)[2]; MID_RHS_MATCH_FROM(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[123.1.85.147:received] X-ThisMailContainsUnwantedMimeParts: N 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