From: Alex Kost <alezost@gmail.com>
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: guix-devel@gnu.org
Subject: Re: delete profile
Date: Thu, 16 Mar 2017 12:13:48 +0300 [thread overview]
Message-ID: <87var91t4j.fsf@gmail.com> (raw)
In-Reply-To: <20170314151844.GB15269@mail.thebird.nl> (Pjotr Prins's message of "Tue, 14 Mar 2017 15:18:44 +0000")
Pjotr Prins (2017-03-14 15:18 +0000) wrote:
> On Tue, Mar 14, 2017 at 05:28:52PM +0300, Alex Kost wrote:
>> No, "$HOME/guix-test-profile" was not a symlink to
>> "/var/guix/profiles/...". Try this:
>
> Hmmm. You are right. ~/.guix-profile, meanwile, does point inside
> /var/guix.
Yes, "~/.guix-profile" is the only "special" profile that uses this
additional level of symlinking. Profiles that you create with "guix
package -p ... -i ..." always point directly to store.
> I have wondered before how GC works on profiles not in /var/guix.
>
> Where does it store that state? In the database?
As Ludovic wrote, the links to the created profile generations are put
in "/var/guix/gcroots/auto" and "guix gc" does not clear the store of
these "registered gc roots".
> I mean, if I simply
> remove the symlink
>
> lrwxrwxrwx 1 wrk 502 51 Feb 19 09:38 guix-build-system-1-link -> /gnu/store/0lyv2p35ziymd6xjrfxy8sp502n2ii5d-profile
>
> how does Guix know it can GC /gnu/store/0lyv2p35ziymd6xjrfxy8sp502n2ii5d-profile?
After you remove "foo-1-link", the according link in
"/var/guix/gcroots/auto" will become dead, so "guix gc" will remove it
and will clear the store of that profile.
--
Alex
next prev parent reply other threads:[~2017-03-16 9:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-12 17:28 delete profile Federico Beffa
2017-03-13 19:35 ` Alex Kost
2017-03-14 5:55 ` Pjotr Prins
2017-03-14 8:42 ` Federico Beffa
2017-03-14 14:36 ` Alex Kost
2017-03-14 16:43 ` Federico Beffa
2017-03-15 11:09 ` Andy Wingo
2017-03-15 16:00 ` Ludovic Courtès
2017-03-16 9:13 ` Alex Kost
2017-03-14 14:28 ` Alex Kost
2017-03-14 15:18 ` Pjotr Prins
2017-03-16 9:13 ` Alex Kost [this message]
2017-03-16 12:18 ` Pjotr Prins
2017-03-14 13:26 ` 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=87var91t4j.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=guix-devel@gnu.org \
--cc=pjotr.public12@thebird.nl \
/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).