unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Mykola Nikishov <mn@mn.com.ua>
To: help-guix@gnu.org
Subject: How to prevent incomplete build results from being garbage collected?
Date: Sun, 10 Apr 2022 10:34:54 +0300	[thread overview]
Message-ID: <87tub11jdt.fsf@think> (raw)

Hi there,

I'm trying to build a package that fails. In the meantime, I'd like to
reclaim some disk space by collecting garbage. After that, all build
results for such package are gone and rebuilding it next time just
wastes bandwidth and CPU cycles by re-downloading and re-building the
same stuff:

#+begin_example
  guix build <PACKAGE>
  guix gc
  guix build <PACKAGE>
#+end_example

Using --root=FILE with guix build does not help, I suppose it would help
only for successful build.

How could I retain build results regardless if build was successful or
not?

-- 
Mykola

Libre/Free Java Software Developer
https://manandbytes.gitlab.io/



             reply	other threads:[~2022-04-10  7:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-10  7:34 Mykola Nikishov [this message]
2022-04-16  8:02 ` How to prevent incomplete build results from being garbage collected? James Thomas
2022-04-28  9:05   ` zimoun

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=87tub11jdt.fsf@think \
    --to=mn@mn.com.ua \
    --cc=help-guix@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).