From nobody Sat Aug 6 06:51:49 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 4M0DJQ146Mz4YBhK for ; Sat, 6 Aug 2022 07:15:34 +0000 (UTC) (envelope-from yuri@FreeBSD.org) Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id 4M0DJP3STVz3sVv; Sat, 6 Aug 2022 07:15:33 +0000 (UTC) (envelope-from yuri@FreeBSD.org) Received: from [192.168.5.3] ([76.132.248.201]) (authenticated bits=0) by shell1.rawbw.com (8.15.1/8.15.1) with ESMTPSA id 2766poEs077976 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Fri, 5 Aug 2022 23:51:50 -0700 (PDT) (envelope-from yuri@FreeBSD.org) X-Authentication-Warning: shell1.rawbw.com: Host [76.132.248.201] claimed to be [192.168.5.3] Message-ID: Date: Fri, 5 Aug 2022 23:51:49 -0700 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:91.0) Gecko/20100101 Thunderbird/91.11.0 Subject: Re: Why NOARCH packages aren't available on all architectures? Content-Language: en-US To: Mark Millard , "yuri@freebsd.org" , freebsd-ports@freebsd.org References: <689E23B1-BBF8-4A08-AC20-2CFABFB981AA.ref@yahoo.com> <689E23B1-BBF8-4A08-AC20-2CFABFB981AA@yahoo.com> From: Yuri In-Reply-To: <689E23B1-BBF8-4A08-AC20-2CFABFB981AA@yahoo.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4M0DJP3STVz3sVv X-Spamd-Bar: + Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=softfail (mx1.freebsd.org: 198.144.192.42 is neither permitted nor denied by domain of yuri@FreeBSD.org) smtp.mailfrom=yuri@FreeBSD.org X-Spamd-Result: default: False [1.50 / 15.00]; VIOLATED_DIRECT_SPF(3.50)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCVD_NO_TLS_LAST(0.10)[]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FREEFALL_USER(0.00)[yuri]; DMARC_NA(0.00)[freebsd.org]; FROM_HAS_DN(0.00)[]; MLMMJ_DEST(0.00)[freebsd-ports@freebsd.org]; RCPT_COUNT_THREE(0.00)[3]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; ASN(0.00)[asn:7961, ipnet:198.144.192.0/19, country:US]; HAS_XAW(0.00)[]; TO_DN_SOME(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; R_SPF_SOFTFAIL(0.00)[~all:c]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_TO(0.00)[yahoo.com,FreeBSD.org,freebsd.org]; MIME_TRACE(0.00)[0:+]; R_DKIM_NA(0.00)[]; GREYLIST(0.00)[pass,body] X-ThisMailContainsUnwantedMimeParts: N On 8/5/22 13:19, Mark Millard wrote: > Part of what is going on is that having a NOARCH end result > can still involve the build using build-environment-ARCH > specific toolchains. You are implying that NOARCH packages should be built on each architecture individually. But NOARCH packages fit any architecture, regardless of where they are built. Once successfully built on one architecture they should become available for all architectures. It's amazing that this isn't what is happening. Yuri