From nobody Sat Aug 6 08:09:38 2022 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 4M0FVw420gz4YKLb for ; Sat, 6 Aug 2022 08:09:44 +0000 (UTC) (envelope-from se@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4M0FVw3VbRz3yJW; Sat, 6 Aug 2022 08:09:44 +0000 (UTC) (envelope-from se@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1659773384; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Zk5PToNPzqtaUo1c4MC2Ew5ONA6Mp6Y609IYSVlX2hs=; b=ExMFw+5/YJZbPdun+pBmAXA2mgXepDghB9xn8kkpJg022cbUgYlN7/7NQMpJmeDU29yzoc x7j3MHd6n2cOCDNH+RE7lrmWpAbxj0aI+DEVDs2wvt6j1p5rnjPxqUKri6Pacw5QZWxGX/ rRBx62cvfXuNv7SvXfEq+bb/JGb9MmY00fAqoc86RhdIL+FQHVClh6dAAWpqV1xbJjPKei 48crul+JpixCrckouhJ69tV8EiOwUIVEHpY1TyyCdR6L+YbgvH27RGTIHjR7mz4FewEmbJ OoLActWQsIIfuD/79kczgeV/L/HljrQ4EGu6aUai7JpRp8aUmhIvmGyHUCWKSA== Received: from [IPV6:2003:cd:5f1a:d200:8c26:2312:494e:dfee] (p200300cd5f1ad2008c262312494edfee.dip0.t-ipconnect.de [IPv6:2003:cd:5f1a:d200:8c26:2312:494e:dfee]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: se/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4M0FVv51KGz10QB; Sat, 6 Aug 2022 08:09:43 +0000 (UTC) (envelope-from se@FreeBSD.org) Message-ID: <481a8589-d2d0-33bf-094a-2a8739053da0@FreeBSD.org> Date: Sat, 6 Aug 2022 10:09:38 +0200 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 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.1.0 Subject: Re: Why NOARCH packages aren't available on all architectures? Content-Language: de-DE, en-US To: freebsd-ports@freebsd.org References: <689E23B1-BBF8-4A08-AC20-2CFABFB981AA.ref@yahoo.com> <689E23B1-BBF8-4A08-AC20-2CFABFB981AA@yahoo.com> From: Stefan Esser Cc: Tatsuki Makino , Mark Millard , Yuri In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1659773384; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Zk5PToNPzqtaUo1c4MC2Ew5ONA6Mp6Y609IYSVlX2hs=; b=KRJbue0p3UXiVmE89yR8LhO1H08w5K8m1bcuvkyoghG7l6Jem9nXM+2nIkElU53hfb13K4 j+FRe6lZ7tBMZvj7qbcsePWT2vvUWpZ3OwefBb4tvAER8DMVdtgwBdKnlG8v2Gwg+/RyUV bMISEMErjS7Mr3Rb1OAQBgYAdFcc/JsB7nevr4heJgUYUQA3QAZercXGycgwa4v4x2n+oP VPNAAlQWG9wbX7uvFGlkGfdg063qEGvL6R2UAf45rOaYxlcnzd3PbdejMmruTlF8XrCSB2 TQxwv9AIQFgCSRjSENkXrmlpkUX8wvjwuc32mPbIxt40AhJQ8Dxt6MbDeY6nsw== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1659773384; a=rsa-sha256; cv=none; b=iUA0PpRFIBQTDZIp1jCXIwrFYckdirpZ2HJckPn9WHA+D+A+xQqqIKE3YizLDSRjZoZ6Ps N9PkZADP1iF5MuxpB3v9+Fut50r/Fye7eTQ1eRPCbO9KvwMBdHIXS/nlaHcwmzoV48ZK1b sRC1slK91EDtGKz42lusXWquCrJsJMGxVpveLq25oP4TE8rxgoAkE5lMlny3sVU0xkRlz3 z1iwz35Eq+EbjEUtFZM4NSd+xmRS7ZkyPc5vSw+/YIcTsGzXTXbA4cWRjA7CjWNToul96T UZx5ajwv/cy0200dOSHQRxgnxJbhb6U0F4zDTHbbOYUhpqp+RGTywetbPIOrDA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N Am 06.08.22 um 09:40 schrieb Tatsuki Makino: > Hmmm, it seems to me that this is a problem due to the difference between noarch being a tag-like classification and packages being provided in a tree-like classification for each architecture. Yes, this is the result of how NO_ARCH packages are being built on each architecture. The NO_ARCH macro causes the machine part of the architecture to be set to "*" in the package, but it does not actually lead to such packages being shared between architectures. In a prior discussion about this topic bapt mentioned that ports marked as NO_ARCH should only be built once and then distributed to all repositories. But this is not a trivial change to the build system. > And other things, like that reason for the file system not being able to create hard links of directory. > Like, we can' t bypass the tree map and follow it... etc... I'd think that a package marked NO_ARCH that has successfully been built on one architecture could be made available in all repositories. But such packages would not be available if depended on in the current build batch. One possible solution could be to build all NO_ARCH packages (and all their build dependencies) on one architecture that has fast package builders, e.g. amd64, then to seed all repositories for all architectures with the resulting NO_ARCH packages before they are started based on the same ports commit that had been used to generate those NO_ARCH packages. This would make at least all NO_ARCH packages available that can be built in e.g. amd64. If some have not been provided in the initial NO_ARCH build on amd64, they still might be built for individual architectures with all the architecture dependent ports. Such a procedure would require finishing the initial NO_ARCH build before the builds for all architectures are started, but if NO_ARCH packages were built on the fastest package builders, this could even reduce overall build times. This would make more NO_ARCH packages available than are currently provided, but if the reason a NO_ARCH package cannot be built on some architecture is a missing interpreter (e.g. Python version 3.9) than this interpreter will also be required at run time - the NO_ARCH package would therefore be of little use ... Regards, STefan