unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: bug-guix@gnu.org
Subject: Re: guix-gc
Date: Thu, 10 Jan 2013 11:04:21 +0100	[thread overview]
Message-ID: <201301101104.22164.andreas@enge.fr> (raw)
In-Reply-To: <8738yfp4j7.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1167 bytes --]

Am Sonntag, 6. Januar 2013 schrieb Ludovic Courtès:
> Commit fe8ff02 adds a ‘guix-gc’ command to invoke the GC, similar to
> part of the ‘nix-store’ command.  Below is a copy of the manual.
> 
> Comments welcome!

When running "guix-gc" without specifying any root, the complete content of 
/nix/store was classified as dead. This looks a bit excessive to me; should 
not at least the gnu build system that would be used to build a package 
with the currently installed guix be preserved? Even if the user has not 
installed gcc in his environement, for instance, the "current" gcc should 
be kept, whereas any older gcc (I had quite a few of them corresponding to 
several versions of guix) should be deleted.

If I see it correctly, this means that the output of
   guix-build hello --dry-run
should be kept in the store.


I also got the following error on the first run:

deleting `/nix/store/j29s9129di8lzx7xbc9rj0ywx05pivij-readline-6.2'
error: build failed: getting status of 
`/nix/store/j29s9129di8lzx7xbc9rj0ywx05pivij-readline-6.2': No such file or 
directory

But the next run worked and deleted everything.

Andreas

[-- Attachment #2: Type: text/html, Size: 4730 bytes --]

  reply	other threads:[~2013-01-10 10:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-05 23:57 guix-gc Ludovic Courtès
2013-01-10 10:04 ` Andreas Enge [this message]
2013-01-10 12:40   ` guix-gc Ludovic Courtès
2013-01-19 13:00     ` guix-gc Andreas Enge
2013-01-22 21:56       ` guix-gc Ludovic Courtès
2013-01-26 13:58         ` guix-gc Andreas Enge

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=201301101104.22164.andreas@enge.fr \
    --to=andreas@enge.fr \
    --cc=bug-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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).