From: Leo Famulari <leo@famulari.name>
To: raingloom <raingloom@riseup.net>
Cc: help-guix@gnu.org
Subject: Re: GUIX_LOCPATH message over and over again
Date: Sat, 23 May 2020 14:32:42 -0400 [thread overview]
Message-ID: <20200523183242.GA2523@jasmine.lan> (raw)
In-Reply-To: <20200523160602.4961dd52@riseup.net>
On Sat, May 23, 2020 at 04:06:02PM +0200, raingloom wrote:
> This should probably be clarified better in the docs, because I
> installed Guix on top of Ubuntu recently and even though I've set it up
> correctly once on Arch, it was rather confusing to me why I was getting
> that message.
> I think the frequency with which people ask about it is enough proof
> that the docs don't cover properly all the issues that beginners face.
Yup! It's been a pain point for a long time, and we've been slowly
chipping away at it.
We started discussing it here recently:
https://lists.gnu.org/archive/html/guix-devel/2020-03/msg00260.html
Maybe you have some ideas?
next prev parent reply other threads:[~2020-05-23 18:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 15:17 GUIX_LOCPATH message over and over again Ekaitz Zarraga
2020-05-19 15:46 ` Leo Famulari
2020-05-23 14:06 ` raingloom
2020-05-23 18:32 ` Leo Famulari [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-05-20 6:03 Jérémy Korwin-Zmijowski
2020-05-20 11:02 ` zimoun
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=20200523183242.GA2523@jasmine.lan \
--to=leo@famulari.name \
--cc=help-guix@gnu.org \
--cc=raingloom@riseup.net \
/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).