From: swedebugia <swedebugia@riseup.net>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: About /var/guix/profiles and guix pull generations
Date: Wed, 26 Dec 2018 01:09:20 +0100 [thread overview]
Message-ID: <a308c0f2-6822-752c-4f8c-ef1950f32f16@riseup.net> (raw)
In-Reply-To: <87k1jxigrj.fsf@ambrevar.xyz>
On 2018-12-25 19:49, Pierre Neidhardt wrote:
>
>> Why duplicate lines here?
>
> They are not duplicated, the arguments are
>
>> + profile
>> + (string-append (config-directory #:ensure? #f) "/current")))
>
> so one is for the user profile, one is for the Guix "checkout".
>
>> : +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).")
>> : + profile
>> : + (string-append (config-directory #:ensure? #f) "/current")))
>>
>> I think this is quite long and I don't understand your phrase about broken
>> symlinks.
>
> In /var/guix/gcroots/auto, you'll find symlinks to custom profiles,
> e.g. ~/.my-guix-profile.
> If you remove ~/.my-guix-profile, then the symlink in /var/guix/gcroots/auto
> will be broken and automatically removed by Guix. Makes sense?
>
> Can you suggest a better phrasing?
>
>> Could you write a new section "Freeing up space in GuixSD" in the manual instead
>> and refer to that here instead?
>
> That could be a good solution indeed. What do you people think?
I already sent a patch for the manual on Marks suggestion regarding free
space. See
https://lists.gnu.org/archive/html/guix-patches/2018-11/msg00243.html
You are welcome to adopt it if you think it can make it into the manual
that way. At that time I did not know about these stale checkouts you
are referring to. I think guix should generally clean up after itself
and be very clear about what factors cause it to consume space.
--
Cheers Swedebugia
next prev parent reply other threads:[~2018-12-26 0:02 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
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 [this message]
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=a308c0f2-6822-752c-4f8c-ef1950f32f16@riseup.net \
--to=swedebugia@riseup.net \
--cc=help-guix@gnu.org \
--cc=mail@ambrevar.xyz \
/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).