From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Simon South <simon@simonsouth.net>, Help guix <help-guix@gnu.org>
Subject: Re: Specifying dependencies among package outputs?
Date: Fri, 16 Oct 2020 19:32:11 +0200 [thread overview]
Message-ID: <754748c691269aaab492707b26c0562d@tobias.gr> (raw)
In-Reply-To: <87lfg7aw95.fsf@simonsouth.net>
On 2020-10-16 1:45, Simon South wrote:
> Tobias Geerinckx-Rice <me@tobias.gr> writes:
>> Sound good?
>
> Yep, that feels like a natural division.
I've pushed a polished version of the example to master: man pages now
end up in the same output as their command. Man section numbers align
with the {s,}bin convention so that was easy.
The Texinfo manual less so, as it covers all of Knot. I see no better
solution than to ship it separately. For 'info knot' to work one must
install (the tiny) knot:doc alongside the desired output(s).
Kind regards,
T G-R
Sent from a Web browser. Excuse or enjoy my brevity.
prev parent reply other threads:[~2020-10-16 17:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-14 22:32 Specifying dependencies among package outputs? Simon South
2020-10-15 0:07 ` Julien Lepiller
2020-10-15 0:37 ` Tobias Geerinckx-Rice
2020-10-15 0:43 ` Tobias Geerinckx-Rice
2020-10-15 11:44 ` zimoun
2020-10-15 14:54 ` Simon South
2020-10-15 22:26 ` Tobias Geerinckx-Rice
2020-10-15 23:45 ` Simon South
2020-10-16 17:32 ` Tobias Geerinckx-Rice [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=754748c691269aaab492707b26c0562d@tobias.gr \
--to=me@tobias.gr \
--cc=help-guix@gnu.org \
--cc=simon@simonsouth.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).