From nobody Mon Sep 25 22:33:55 2023 X-Original-To: freebsd-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 4Rvd321XpJz4v9TJ for ; Mon, 25 Sep 2023 22:34:22 +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 4Rvd3120TGz4SZW; Mon, 25 Sep 2023 22:34:20 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Authentication-Results: mx1.freebsd.org; none Received: from kalamity.joker.local (123-1-80-101.area1b.commufa.jp [123.1.80.101]) (authenticated bits=0) by www121.sakura.ne.jp (8.16.1/8.16.1/[SAKURA-WEB]/20201212) with ESMTPA id 38PMXtdE020239; Tue, 26 Sep 2023 07:33:56 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) Date: Tue, 26 Sep 2023 07:33:55 +0900 From: Tomoaki AOKI To: Chris Cc: Guido Falsi , Gareth de Vaux , freebsd-ports@freebsd.org Subject: Re: dns/bind916 builds rust unexpectedly Message-Id: <20230926073355.a3fc4bbc3595fd08e1080470@dec.sakura.ne.jp> In-Reply-To: References: <1e05be67-cb15-964e-c78b-e74e714257a9@FreeBSD.org> <343f2abb-6a3e-0193-f4bc-5db69c8021f5@FreeBSD.org> Organization: Junchoon corps X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd14.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-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:7684, ipnet:153.125.128.0/18, country:JP] X-Rspamd-Queue-Id: 4Rvd3120TGz4SZW On Mon, 25 Sep 2023 13:03:24 -0700 Chris wrote: > On 2023-09-25 11:38, Guido Falsi wrote: > > On 25/09/23 20:33, Guido Falsi wrote: > >> On 25/09/23 19:50, Gareth de Vaux wrote: > >>> On Mon 2023-09-25 (17:38), Guido Falsi wrote: > >>>> This one, which calls in py-cryptography which requires rust. > >>> > >>> Thanks > >>> > >>>> There is a more general aspect to this. In the rest of the unix world > >>>> software is now almost universally build using CI systems and buildboxes, > >>>> people use binary packages almost all the time in linux. Developers don't > >>>> care to keep low overhead in their builds and with dependency. The ports > >>>> tree cannot mitigate this external pressure. > >>> > >>> Understood. Though the situation you point out has been around for decades > >>> and this is the first time I've encountered such a chaotic result. > >>> > > > > Anyway, in this specific case, simply be ready to see rust being requested > > as a > > build dependency of more and more software. > > > > Not that I approve, or disapprove, for that matter, of it, but this is the > > direction we're headed to. > > Couldn't one overcome this problem by using an antioxidant, or even a rust > remover? ;-) > Sorry. Couldn't resist. The largest pain about rust for me is that all dependencies (including BUILD_DEPEND'ed ones) are bumped when rust is updated. It's maybe because of (forcibly) statically linked object, like crt.o in C, is incorporated. If it's true, splitting them into individual port would decrease the needs to bump dependencies, to only when the source for those objects are modified and/or changes in such as code generator makes the resulting objects backwward incompatible way. > >> One can drive a car without using seat belts for years without any injury > >> [1], dies this mean seat belts are unnecessary? > >> > >> [1] if he is lucky enough to never cause or be involved (without any blame) > >> in a crash, even minor one. -- Tomoaki AOKI