From: ludo@gnu.org (Ludovic Courtès)
To: carl hansen <carlhansen1234@gmail.com>
Cc: 22402@debbugs.gnu.org
Subject: bug#22402: info guix pages
Date: Tue, 19 Jan 2016 11:45:09 +0100 [thread overview]
Message-ID: <87powxc0ga.fsf@gnu.org> (raw)
In-Reply-To: <CAHEkXCRYCW0YWz4Y-NRu-jq4D2OTyW23E3Kkko9qG6auX-duRg@mail.gmail.com> (carl hansen's message of "Tue, 19 Jan 2016 01:34:46 -0800")
carl hansen <carlhansen1234@gmail.com> skribis:
> Yes, that is the case, there is no mystery, there is indeed a
> /root/.guix-profile/share/info/guix.info
> and there is NOT a
> ~user/.guix-profile/share/info/guix.info
OK.
> However I consider that a bug. Here I am a user, using guix, and I expect
> "info guix" to work. Why would the user have to switch to root just to read
> this one info file? After installing guix, I would expect guix.info to be
> in my defalt .guix-profile, or a least a notice of how to install
> guix.info. ( coping and linking I know how to do, that's not the problem.
> It's a question
> of creating a polished piece of software.)
Yeah, I agree this is bad. On GuixSD there’s no such problem because
Guix is installed system-wide, so “info guix” always picks up the
system-wide guix.info at least.
> Would "guix package -i guix" do the right thing? That seems all
> wrong, would install stuff I already have.
It would do the trick, yes.
I’m not sure how to fix that problem on foreign distros. Suggestions
welcome.
Ludo’.
next prev parent reply other threads:[~2016-01-19 10:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 23:43 bug#22402: info guix pages carl hansen
2016-01-19 1:47 ` Leo Famulari
2016-01-19 3:55 ` carl hansen
2016-01-19 9:01 ` Ludovic Courtès
2016-01-19 9:34 ` carl hansen
2016-01-19 10:45 ` Ludovic Courtès [this message]
2016-01-19 16:42 ` Efraim Flashner
2016-01-19 17:17 ` Thompson, David
2016-01-19 22:02 ` Leo Famulari
2016-01-20 0:45 ` carl hansen
2016-01-20 4:24 ` Leo Famulari
2016-01-21 1:26 ` carl hansen
2016-01-21 3:21 ` Leo Famulari
2016-01-20 23:23 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87powxc0ga.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=22402@debbugs.gnu.org \
--cc=carlhansen1234@gmail.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.