From: vapnik spaknik via <help-guix@gnu.org>
To: help-guix@gnu.org, Pierre Neidhardt <mail@ambrevar.xyz>
Subject: Re: profile symlinks structure
Date: Mon, 25 May 2020 10:26:36 +0000 (UTC) [thread overview]
Message-ID: <34750776.4383586.1590402396826@mail.yahoo.com> (raw)
In-Reply-To: <87o8qcphr3.fsf@ambrevar.xyz>
Thankyou.
Btw, the email at the top of this thread was sent by mistake before I had finished writing it. I will continue correspondence on the next thread which contains the complete message.
On Monday, May 25, 2020, 08:59:33 AM GMT+1, Pierre Neidhardt <mail@ambrevar.xyz> wrote:
Hi!
It seems that you've got it right so far! :)
You'll find more profiles in /var/guix/gcroots/auto: these are the roots
that are automatically created, e.g. when using the `guix package --profile=...`
among others.
prev parent reply other threads:[~2020-05-25 10:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1313331337.2299626.1590332180730.ref@mail.yahoo.com>
2020-05-24 14:56 ` profile symlinks structure vapnik spaknik
2020-05-25 7:59 ` Pierre Neidhardt
2020-05-25 10:26 ` vapnik spaknik via [this message]
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=34750776.4383586.1590402396826@mail.yahoo.com \
--to=help-guix@gnu.org \
--cc=mail@ambrevar.xyz \
--cc=vapniks@yahoo.com \
/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).