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: [gentoo-dev] Portage and languages with built-in cache support
Date: Tue, 25 Apr 2023 13:07:22 +0500	[thread overview]
Message-ID: <ZEeKOtseVgn810ks@sysrq.in> (raw)

Hello,

Portage can use ccache and sccache to speed up builds, but some
languages (like Go and Nim) support caches out-of-the-box. It's not fair
that we can't use them.

I'd like to start discussion on this topic. What should be the preferred
method of handling build caches?

I think adding more stuff to Portage is a bad idea, and caches should be
handled by corresponding "${lang}-utils" eclasses. It can be as simple
as checking some variable, passing necessary flags and placing a couple
of 'addwrite' calls for sandbox.

Of course, such feature needs to be strictly opt-in.


             reply	other threads:[~2023-04-25  8:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-25  8:07 Anna (cybertailor) Vyalkova [this message]
2023-04-25 14:09 ` [gentoo-dev] Portage and languages with built-in cache support Maciej Barć
2023-04-26 13:43   ` Anna (cybertailor) Vyalkova
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=ZEeKOtseVgn810ks@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