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 20CBC15806E for ; Thu, 1 Jun 2023 16:03:27 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D8D93E07EC; Thu, 1 Jun 2023 16:03:22 +0000 (UTC) Received: from smtp.gentoo.org (mail.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (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 8DB61E078A for ; Thu, 1 Jun 2023 16:03:22 +0000 (UTC) Received: (nullmailer pid 32531 invoked by uid 1000); Thu, 01 Jun 2023 16:03:19 -0000 Date: Thu, 1 Jun 2023 11:03:19 -0500 From: William Hubbs To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Portage and languages with built-in cache support Message-ID: Mail-Followup-To: gentoo-dev@lists.gentoo.org References: <79be9b1f-7f4b-d652-6aa1-a4154adcb6c4@gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="si/EjaBr/SN66dZh" Content-Disposition: inline In-Reply-To: X-Archives-Salt: cc2e9fab-4db0-4064-b881-beb522a25c17 X-Archives-Hash: accf7f45a791052cf66aff81db2893ad --si/EjaBr/SN66dZh Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Apr 26, 2023 at 06:43:04PM +0500, Anna (cybertailor) Vyalkova wrote: > On 2023-04-25 16:09, Maciej Bar=C4=87 wrote: > > You would also have to have correct permissions on cache dirs=20 > > (root:portage or portage:portage) this also means that the cache dir=20 > > will have to be set during build explicitly. > > Do both Nim and Go support setting it? >=20 > Yes. For Nim it would be something like that: >=20 > # nim.cfg > --nimcache:"${EPREFIX}/var/cache/nim/${CATEGORY}/${PN}" >=20 > And for Go: >=20 > export GOCACHE=3D"${EPREFIX}/var/cache/go" This would be very easy to do in the go-module eclass, but we would need to test how it works with go upgrades. This cache is for compiled objects, so I hope it would clean the cache and restart it with every go upgrade since compiled go objects are not compatible between go versions. William --si/EjaBr/SN66dZh Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABECAB0WIQTVeuxEZo4uUHOkQAluVBb0MMRlOAUCZHjBQAAKCRBuVBb0MMRl OI4SAJ9IjGrukSZCV6Y1uGs85eILMsrITgCfaTczeQRuyQ+ojSkMdnvCHKHC5sQ= =PTEz -----END PGP SIGNATURE----- --si/EjaBr/SN66dZh--