From nobody Thu Feb 16 12:48:30 2023 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 4PHZW657JBz3qPXD for ; Thu, 16 Feb 2023 12:48:34 +0000 (UTC) (envelope-from SRS0=QyCk=6M=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4PHZW61S9Jz3JmY for ; Thu, 16 Feb 2023 12:48:33 +0000 (UTC) (envelope-from SRS0=QyCk=6M=quip.cz=000.fbsd@elsa.codelab.cz) Authentication-Results: mx1.freebsd.org; none Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 3563FD788C; Thu, 16 Feb 2023 13:48:31 +0100 (CET) Received: from [192.168.145.50] (ip-89-177-27-225.bb.vodafone.cz [89.177.27.225]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 66109D7885; Thu, 16 Feb 2023 13:48:30 +0100 (CET) Message-ID: <214ba14d-120e-764d-c7ef-f9be8536a711@quip.cz> Date: Thu, 16 Feb 2023 13:48:30 +0100 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 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.7.1 Subject: Re: How poudriere's PACKAGE_FETCH_WHITELIST should work? Content-Language: cs-Cestina To: ports@freebsd.org References: <9B296C55-6F06-4E10-9056-ECAD05630920.ref@yahoo.com> <9B296C55-6F06-4E10-9056-ECAD05630920@yahoo.com> <287633b4-1363-4d91-a572-bc0960f592e5@quip.cz> From: Miroslav Lachman <000.fbsd@quip.cz> Cc: Mark Millard , Tatsuki Makino In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4PHZW61S9Jz3JmY X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:42000, ipnet:94.124.104.0/21, country:CZ] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On 16/02/2023 03:10, Mark Millard wrote: [..] >> # note that I avoided recreating llvm13 and llvm15 that way :) >> > > Turns out my notes did not apply: the person I replied to was > using quarterly and so things were apparently not changing. > > But I'd not checked the transitive closures for the various > ports involved for the 2023Q1 context. Using rust and its > curl dependency as an example: > > curl in turn depends on at least devel/pkgconf , lang/perl5.32 , > security/ca_root_nss , www/libnghttp2 , security/libssh2 , > and dns/libpsl . So there is a fair list of things that can > cause curl to rebuild, which in turn leads to rust potentially > rebuilding, even if the rebuild result for rust ends up not > being installed for lack of a version bump: existing install > is still expected to be compatible given the lack of a version > bump. Yes, now it all make sense! So it seems llvm / rust / gcc will be almost always (re)built because of their dependencies changes a lot. I'll try to dig deeper into this subject, maybe I will try to pre fetch dependencies of llvm, gcc and rust as well (if they don't have a different options then we need) Thank you! Miroslav Lachman