From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 99B50158041 for ; Tue, 26 Mar 2024 10:32:33 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id DB80BE2A19; Tue, 26 Mar 2024 10:32:26 +0000 (UTC) Received: from m4.out1.mxs.au (m4.out1.mxs.au [110.232.143.182]) (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) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 3B5C9E2A01 for ; Tue, 26 Mar 2024 10:32:25 +0000 (UTC) Received: from fe.s3.ax.email (fe.s3.ax.email [110.232.143.215]) by out1.mxs.au (Halon) with ESMTPS (TLSv1.3) tls TLS_AES_256_GCM_SHA384 id 1e6b9650-eb5c-11ee-ac91-00163c39b365 for ; Tue, 26 Mar 2024 21:32:17 +1100 (AEDT) Authentication-Results: fe.s3.ax.email; dkim=pass header.d=kenworthy.id.au header.b="O/DRdn6e" Received: from be4.s3.ax.email (10.40.10.219) by fe.s3.ax.email (Axigen) with (TLS_AES_256_GCM_SHA384 encrypted) ESMTPSA id 07DA8E; Tue, 26 Mar 2024 21:32:17 +1100 DKIM-Signature: v=1; a=rsa-sha256; d=kenworthy.id.au; s=axigen; c=relaxed/relaxed; q=dns/txt; h=from:date:to:cc:message-id:subject; bh=sHc/+Der1nocqtpNNbe6uQmHfB+A0lT6ZcyZh5tI12k=; b=O/DRdn6eQnWjHE3P9j9vgAmkHlCBv9HPIBkzeKSCt7yJMc/Mx37uOg6Q5TMosHq0ui9zCa6wfBaMO9ad+aQVpHfBpDtnHs8Ll7Ow1TRaYCFwDLkiCz3vaTI/IgwJw2Un8K3zeJM9o0DyVn1z68sMaX4g2Gqc4IjEj2gGlwBbbSP/2QMXkO7brPjQDiJvPgI6oSkKGjibAK89VEMKlxPVo5X5itlbUUUpcGXb4lruyaFfwrqw/ZD4HqZE5OUgIgkESXzDmrhq+o940rnLUaMj4Kc44uxciQuBjP/6IpCVF6tMlVRJffguUwu/hNUequeX3bCRiIiIDzWSJYE6loz0mg==; Authentication-Results: be4.s3.ax.email; dkim=none Authentication-Results: be4.s3.ax.email; spf=pass smtp.mailfrom=bill@kenworthy.id.au Received: from fe.s2.ax.email (10.40.10.210) by be4.s3.ax.email (Axigen) with (TLS_AES_256_GCM_SHA384 encrypted) ESMTPSA id 39023B; Tue, 26 Mar 2024 21:32:17 +1100 Authentication-Results: fe.s2.ax.email; dkim=none Received: from mail.infra.localdomain (10.40.10.201) by fe.s2.ax.email (Axigen) with (ECDHE-RSA-AES128-GCM-SHA256 encrypted) ESMTPSA id 264774; Tue, 26 Mar 2024 21:32:17 +1100 Received: from localhost (mail.infra.localdomain [127.0.0.1]) by mail.infra.localdomain (Postfix) with ESMTP id 4C33F954E574D for ; Tue, 26 Mar 2024 18:32:16 +0800 (AWST) X-Virus-Scanned: amavisd-new at localdomain Received: from mail.infra.localdomain ([127.0.0.1]) by localhost (mail.infra.localdomain [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NIhYXLhhD0ti for ; Tue, 26 Mar 2024 18:32:10 +0800 (AWST) Date: Tue, 26 Mar 2024 21:32:05 +1100 From: William KENWORTHY To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] New profiles 23.0 User-Agent: K-9 Mail for Android In-Reply-To: References: <5768289.DvuYhMxLoT@cube> <10443877.nUPlyArG6x@rogueboard> <3803243.kQq0lBPeGt@rogueboard> Message-ID: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: multipart/alternative; boundary=----I9RWJWNK9QVXEBJB5JZPRRAY0A1LWU Content-Transfer-Encoding: 7bit DomainKey-Status: no signature DKIM-Status: good Received-SPF: X-AXIGEN-DK-Result: No records X-AXIGEN-DKIM-Result: Ok X-Archives-Salt: 1170efcf-ac83-4fcf-99a2-22e2c9ddaf12 X-Archives-Hash: 2f28dd082d74fc2c71ffe1a7bbd5c807 ------I9RWJWNK9QVXEBJB5JZPRRAY0A1LWU Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable I have a question about binaries and the new profile: I have a number of al= most identical architectures that I build binaries for and share across the= similar sytems e=2Eg=2E arm, aarch64, amd64 etc=2E Is deleting the bin host storage (rm -rf ) enough on the buildho= st so I can share/use the binaries for the "emerge -e" on the other hosts? = Or does it have to be a native emerge? BillK ------I9RWJWNK9QVXEBJB5JZPRRAY0A1LWU Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
I have a question about binari= es and the new profile: I have a number of almost identical architectures t= hat I build binaries for and share across the similar sytems e=2Eg=2E arm, = aarch64, amd64 etc=2E

Is deleting the bin host storage (rm -rf <c= ontents>) enough on the buildhost so I can share/use the binaries for th= e "emerge -e" on the other hosts? Or does it have to be a native emerge?BillK
------I9RWJWNK9QVXEBJB5JZPRRAY0A1LWU--