public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Anna (cybertailor) Vyalkova" <cyber+gentoo@sysrq.in>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Portage and languages with built-in cache support
Date: Wed, 26 Apr 2023 18:43:04 +0500	[thread overview]
Message-ID: <ZEkqaJCDXCwDapA5@sysrq.in> (raw)
In-Reply-To: <79be9b1f-7f4b-d652-6aa1-a4154adcb6c4@gentoo.org>

On 2023-04-25 16:09, Maciej Barć wrote:
> You would also have to have correct permissions on cache dirs 
> (root:portage or portage:portage) this also means that the cache dir 
> will have to be set during build explicitly.
> Do both Nim and Go support setting it?

Yes. For Nim it would be something like that:

	# nim.cfg
	--nimcache:"${EPREFIX}/var/cache/nim/${CATEGORY}/${PN}"

And for Go:

	export GOCACHE="${EPREFIX}/var/cache/go"

on some condition.

The only problem is, they don't support cleaning cache automatically. So
it needs to be done manually or with cron.


  reply	other threads:[~2023-04-26 13:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-25  8:07 [gentoo-dev] Portage and languages with built-in cache support Anna (cybertailor) Vyalkova
2023-04-25 14:09 ` Maciej Barć
2023-04-26 13:43   ` Anna (cybertailor) Vyalkova [this message]
2023-06-01 16:03     ` William Hubbs

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZEkqaJCDXCwDapA5@sysrq.in \
    --to=cyber+gentoo@sysrq.in \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox