all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Arun Isaac <arunisaac@systemreboot.net>
To: "Thompson, David" <dthompson2@worcester.edu>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: How do I check out a package w/o installing it?
Date: Wed, 31 Jan 2018 10:44:00 +0530	[thread overview]
Message-ID: <cu7h8r27gpz.fsf@systemreboot.net> (raw)
In-Reply-To: <CAJ=RwfYK7VYKz43Bo9B9btMhJNa5MJkhyV3zcnGEw_px8XTDjw@mail.gmail.com>

"Thompson, David" <dthompson2@worcester.edu> writes:

> On Mon, Jan 29, 2018 at 2:20 PM, Arun Isaac <arunisaac@systemreboot.net> wrote:
>> George myglc2 Clemmer <myglc2@gmail.com> writes:
>>
>>> I tried to use 'guix environment' to check out znc this way ...
>>>
>>> guix environment --ad-hoc znc -- emacs -nw
>>>
>>> the znc man is unavailable ...
>>
>> I have been wondering the same. It would be nice if at least the man and
>> info documentation was available somehow. What needs to be done in this
>> regard?
>
> If you want to use 'man', include the man-db package in your
> environment. If you want to use 'info', include the info-reader
> package (I think).
>
> To be more general, there isn't any "magic" here.  The znc package
> includes man pages in its output directory, but 'man' won't know about
> it unless it's on $MANPATH.  In order to make Guix set the proper
> MANPATH, you need to include man-db because that package is the one
> that defines the native search path for MANPATH.

This makes sense. I also verified it, and it works for me. Thanks!

      parent reply	other threads:[~2018-01-31  5:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-29 19:00 How do I check out a package w/o installing it? George myglc2 Clemmer
2018-01-29 19:20 ` Arun Isaac
2018-01-29 20:46   ` Thompson, David
2018-01-30  0:47     ` myglc2
2018-01-30  1:16       ` Thompson, David
2018-01-30  1:42         ` George myglc2 Clemmer
2018-01-30  2:34           ` Oleg Pykhalov
2018-01-31  5:14     ` Arun Isaac [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cu7h8r27gpz.fsf@systemreboot.net \
    --to=arunisaac@systemreboot.net \
    --cc=dthompson2@worcester.edu \
    --cc=help-guix@gnu.org \
    /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.