From owner-freebsd-ports@freebsd.org Tue Nov 3 10:24:37 2020 Return-Path: Delivered-To: freebsd-ports@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 87BC1453E11 for ; Tue, 3 Nov 2020 10:24:37 +0000 (UTC) (envelope-from mpp302@gmail.com) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 4CQQrP1kStz4vps for ; Tue, 3 Nov 2020 10:24:37 +0000 (UTC) (envelope-from mpp302@gmail.com) Received: by mailman.nyi.freebsd.org (Postfix) id 39658454151; Tue, 3 Nov 2020 10:24:37 +0000 (UTC) Delivered-To: ports@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 392CB454321 for ; Tue, 3 Nov 2020 10:24:37 +0000 (UTC) (envelope-from mpp302@gmail.com) Received: from mail-ed1-f45.google.com (mail-ed1-f45.google.com [209.85.208.45]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CQQrN2fzsz4vs8; Tue, 3 Nov 2020 10:24:36 +0000 (UTC) (envelope-from mpp302@gmail.com) Received: by mail-ed1-f45.google.com with SMTP id e18so6526664edy.6; Tue, 03 Nov 2020 02:24:36 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=bY8Zy5FejRShTTAVXY5cNFBsDE4idQcf+t/55ix9r4c=; b=DpnScET0pEdRCPrlaG6M70kDonCzzCEqaLnWenXSLXd+Upktca/9c3zCKGgrG7t60G s1nCWuvQqniejLvkAyUzLy4/yZGjxo/8p3aZkYER64u+LLHarXoUSF8KKF+GD0Cq5IUU ux7sKtAoAzN60Gfwg4C6yeK5qS1go4TG135ywWhCG9o396BVsvKV5t/SufRWM7gHk/s7 efuyMwYr+z/dB3824vOsBLVRHarqQRhjf6Np9yvpkKd3aHRs8JtzAylbPjW+Xat60SE1 aYfIgQSoEz+UFwBP3XhPpYMpux3Od2ITHq/420w+9G/vPtMX5NWIIeQ6uJTWIU6LQ9Sp ew2Q== X-Gm-Message-State: AOAM5322T/pGkGTzFZmRPVvL7uy11rDDd3qrAIuNTGFSO0nQmnLQpsAF sGtCCFQnbTeVZ8DaI82GgTZOzKCmWSIUFWvJ X-Google-Smtp-Source: ABdhPJxlqH1gwPCaiCDFXp5uRV/m1IlN6L7SeTF3vQJ9El0Nxb8g35N0NUkYc25e4AGHi1/rStQmyQ== X-Received: by 2002:a50:af21:: with SMTP id g30mr20275979edd.46.1604399074805; Tue, 03 Nov 2020 02:24:34 -0800 (PST) Received: from ?IPv6:2a02:8109:98c0:1bc0:5e5f:67ff:fef4:ffd8? ([2a02:8109:98c0:1bc0:5e5f:67ff:fef4:ffd8]) by smtp.gmail.com with ESMTPSA id p16sm10679762ejz.103.2020.11.03.02.24.33 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 03 Nov 2020 02:24:34 -0800 (PST) Subject: Re: What are the benefits of NO_ARCH? To: Baptiste Daroussin , Stefan Esser Cc: "ports@freebsd.org" References: <823586a7-dfd7-55b2-a7d3-0775a1f2533f@FreeBSD.org> <20201102145018.6jsnumr26feffvgn@ivaldir.net> From: Mateusz Piotrowski <0mp@FreeBSD.org> Message-ID: <7df97983-31fd-2529-171d-c411a137e756@FreeBSD.org> Date: Tue, 3 Nov 2020 11:24:38 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.4.0 MIME-Version: 1.0 In-Reply-To: <20201102145018.6jsnumr26feffvgn@ivaldir.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Rspamd-Queue-Id: 4CQQrN2fzsz4vs8 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of mpp302@gmail.com designates 209.85.208.45 as permitted sender) smtp.mailfrom=mpp302@gmail.com X-Spamd-Result: default: False [-0.75 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17:c]; RCVD_COUNT_THREE(0.00)[3]; FORGED_SENDER(0.30)[0mp@FreeBSD.org,mpp302@gmail.com]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; R_DKIM_NA(0.00)[]; FROM_NEQ_ENVFROM(0.00)[0mp@FreeBSD.org,mpp302@gmail.com]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.89)[-0.885]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-0.99)[-0.986]; MIME_GOOD(-0.10)[text/plain]; SUBJECT_ENDS_QUESTION(1.00)[]; DMARC_NA(0.00)[FreeBSD.org]; NEURAL_SPAM_SHORT(0.12)[0.122]; RCVD_IN_DNSWL_NONE(0.00)[209.85.208.45:from]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.208.45:from]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[ports] X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2020 10:24:37 -0000 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!