Date: Tue, 3 Nov 2020 13:41:54 +0100 From: Mateusz Piotrowski <0mp@FreeBSD.org> To: Baptiste Daroussin <bapt@FreeBSD.org>, Stefan Esser <se@freebsd.org> Cc: "ports@freebsd.org" <ports@FreeBSD.org> Subject: Re: What are the benefits of NO_ARCH? Message-ID: <62c1ec76-450e-15d9-e464-4adb3a9711e4@FreeBSD.org> In-Reply-To: <7df97983-31fd-2529-171d-c411a137e756@FreeBSD.org> References: <823586a7-dfd7-55b2-a7d3-0775a1f2533f@FreeBSD.org> <da2e24cf-a300-2cd6-8a20-afa709d66882@freebsd.org> <20201102145018.6jsnumr26feffvgn@ivaldir.net> <7df97983-31fd-2529-171d-c411a137e756@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11/3/20 11:24 AM, Mateusz Piotrowski wrote: > On 11/2/20 3:50 PM, Baptiste Daroussin wrote: >> On Mon, Nov 02, 2020 at 03:48:34PM +0100, Stefan Esser wrote: >>> Am 02.11.20 um 15:33 schrieb Mateusz Piotrowski: >>>> I wonder if setting NO_ARCH=yes brings any significant benefits to how >>>> our ports collection works. I'd be grateful if you could shed some light >>>> on the importance of setting NO_ARCH whenever possible. >>> NO_ARCH means that there is no need to build packages for each of the >>> supported architectures, e.g. for pure interpreted scripts or data files >>> that do not depend on byte-order and word-size (e.g. many font file >>> formats). >>> >>> The result is reduced resources spent on building the packages, network >>> traffic, disk space on mirrors and on distribution media. >> Yes that is the goal, in practice it is not yet the case, so it is purely >> informational, but that what we are aiming at yes. > > Thanks! > I've added a note to the porter's handbook based on the information you provided: https://svnweb.freebsd.org/doc?view=revision&revision=54671
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?62c1ec76-450e-15d9-e464-4adb3a9711e4>