From: Ricardo Wurmus <rekado@elephly.net>
To: Fulbert <fulbert@bluewin.ch>
Cc: help-guix@gnu.org
Subject: Re: cleaning interrupted build "leftovers" ?
Date: Fri, 28 Aug 2020 12:58:39 +0200 [thread overview]
Message-ID: <87tuwnnijk.fsf@elephly.net> (raw)
In-Reply-To: <20200828103411.GA8514@bluewin.ch>
Fulbert <fulbert@bluewin.ch> writes:
> Yesterday, I interrupted (CTRL+C) the installation of
> linux-libre@5.8.5 when it was in build phase (substitute not
> available yet). Today, a new `guix system reconfigure` has
> found a substitute. I am wondering if, in this situation, my system
> has "leftovers" from the aborted build, that I would need to
> clean… and if so, {where,how} to find it ?!
No, there are no left-overs when aborting a build.
There may be build pre-requisites that are no longer needed, though,
which can be collected by the garbage collector (“guix gc”).
--
Ricardo
next prev parent reply other threads:[~2020-08-28 11:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-28 10:34 cleaning interrupted build "leftovers" ? Fulbert
2020-08-28 10:58 ` Ricardo Wurmus [this message]
2020-08-28 11:03 ` Andreas Enge
2020-08-28 11:11 ` Fulbert
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=87tuwnnijk.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=fulbert@bluewin.ch \
--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).