From: ludo@gnu.org (Ludovic Courtès)
To: 宋文武 <iyzsong@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: wireless-tools: Install the manual pages under $out/share/man
Date: Sat, 29 Nov 2014 21:49:20 +0100 [thread overview]
Message-ID: <87iohxwx4f.fsf@gnu.org> (raw)
In-Reply-To: <87k32e7fys.fsf@gmail.com> ("宋文武"'s message of "Sat, 29 Nov 2014 13:06:51 +0800")
宋文武 <iyzsong@gmail.com> skribis:
> From f961e72823cda48406d0058902c67b6b663da791 Mon Sep 17 00:00:00 2001
> From: =?UTF-8?q?=E5=AE=8B=E6=96=87=E6=AD=A6?= <iyzsong@gmail.com>
> Date: Sat, 29 Nov 2014 12:52:59 +0800
> Subject: [PATCH] gnu: wireless-tools: Install the manual pages under
> $out/share/man.
>
> * gnu/packages/linux.scm (wireless-tools)[origin]: Add snippet.
Thanks, applied.
It may be a good time to get commit access. Could you create an account
on Savannah and let me know?
> We could get rid of MANPATH, if all man pages install to $out/share/man.
Yes, it’s always been the goal to uniformly use share/man.
In core-updates, I’d like to add a build phase at the very end that
checks a few things like that, and aborts on failure. WDYT?
> Assume a suitable PATH is set, try:
> $ guix package -r wireless-tools
> $ env MANPATH= manpath
> Get:
> /run/current-system/profile/man:/home/iyzsong/.guix-profile/share/man
> It's because wireless-tools having man pages in $out/man, after apply
> this patch, we should get:
> /run/current-system/profile/share/man:/home/iyzsong/.guix-profile/share/man
>
> Then `man' will just work even without MANPATH.
Indeed. I didn’t know MANPATH was unneeded in this case.
Thanks!
Ludo’.
next prev parent reply other threads:[~2014-11-29 20:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-29 5:06 [PATCH] gnu: wireless-tools: Install the manual pages under $out/share/man 宋文武
2014-11-29 20:49 ` Ludovic Courtès [this message]
2014-11-30 3:24 ` 宋文武
2014-11-30 16:36 ` 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=87iohxwx4f.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=iyzsong@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 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).