From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: About /var/guix/profiles and guix pull generations
Date: Mon, 10 Dec 2018 09:22:13 +0100 [thread overview]
Message-ID: <87ftv523m2.fsf@ambrevar.xyz> (raw)
In-Reply-To: <87lg4yz6gz.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 856 bytes --]
> I'm not sure what you mean by "Guix checkouts". Do you mean a Git
> checkout of Guix's Git repository? If so, why would deleting it help?
Well, I meant what I wrote in the example below
> guix package --profile=~s --delete-generations=1m
> ...
> (string-append (config-directory #:ensure? #f) "/current")
It deletes the old ~/.config/guix/ profiles. If I'm not wrong, each of those
profiles consume a couple of 100MBs.
So if "checkout" is confusing, what about "Guix copy" instead?
See "(guix) Invoking guix pull" in the manual for terminology.
> "You might also want to delete old non-default profiles pointed to by
> the symlinks in /var/guix/gcroots/auto (broken symlinks in this
> directory will be automatically removed)."
I like it better! I'll use your suggestion.
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2018-12-10 8:22 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-08 10:53 About /var/guix/profiles and guix pull generations Pierre Neidhardt
2018-12-09 4:35 ` Chris Marusich
2018-12-09 12:40 ` Pierre Neidhardt
2018-12-09 12:40 ` Pierre Neidhardt
2018-12-09 13:38 ` Pierre Neidhardt
2018-12-09 22:21 ` Chris Marusich
2018-12-10 8:22 ` Pierre Neidhardt [this message]
2018-12-17 9:12 ` Pierre Neidhardt
2018-12-19 2:48 ` Chris Marusich
2018-12-19 7:49 ` Pierre Neidhardt
2018-12-19 16:16 ` Chris Marusich
2018-12-19 16:28 ` Pierre Neidhardt
2018-12-19 16:31 ` Pierre Neidhardt
2018-12-19 16:49 ` Pierre Neidhardt
2018-12-25 17:51 ` swedebugia
2018-12-25 18:49 ` Pierre Neidhardt
2018-12-26 0:09 ` swedebugia
2020-05-20 8:26 ` Pierre Neidhardt
2018-12-19 13:49 ` GC hints Ludovic Courtès
2018-12-19 14:31 ` Pierre Neidhardt
2018-12-19 14:49 ` Ricardo Wurmus
2018-12-19 16:25 ` Chris Marusich
2018-12-20 12:12 ` Mark H Weaver
2018-12-20 20:03 ` Alex Kost
2018-12-21 8:30 ` Chris Marusich
2018-12-21 8:47 ` swedebugia
2018-12-23 15:58 ` Mark H Weaver
2018-12-25 12:05 ` swedebugia
2018-12-25 14:00 ` Pierre Neidhardt
2019-01-08 22:27 ` Ludovic Courtès
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=87ftv523m2.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=cmmarusich@gmail.com \
--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).