From: "Aurélien Aptel" <aaptel-IBi9RG/b67k@public.gmane.org>
To: Jeffrey Layton <jlayton-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>,
linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Subject: Re: [PATCH] man: generate all man pages from POD files when buidling
Date: Tue, 26 Sep 2017 16:50:35 +0200 [thread overview]
Message-ID: <mpsd16dsedg.fsf@aaptelpc.suse.de> (raw)
In-Reply-To: <1506431475.3182.4.camel-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>
Jeffrey Layton <jlayton-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org> writes:
> Looks reasonable to me, overall. Do we need a new autoconf test for
> pod2man?
>
> What should we do if the build host doesn't have it installed? Error
> out, or disable building the docs?
The latter sounds better. I'll send v2 of this patch.
--
Aurélien Aptel / SUSE Labs Samba Team
GPG: 1839 CB5F 9F5B FB9B AA97 8C99 03C8 A49B 521B D5D3
SUSE Linux GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
next parent reply other threads:[~2017-09-26 14:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170920222053.7977-1-aaptel@suse.com>
[not found] ` <1506431475.3182.4.camel@samba.org>
[not found] ` <1506431475.3182.4.camel-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>
2017-09-26 14:50 ` Aurélien Aptel [this message]
[not found] ` <20170929140303.24880-1-aaptel@suse.com>
[not found] ` <20170929140303.24880-1-aaptel-IBi9RG/b67k@public.gmane.org>
2017-10-06 10:37 ` [PATCH v2] man: generate all man pages from POD files when buidling Jeff Layton
2017-10-23 12:31 ` Jeff Layton
[not found] ` <1508761900.5859.10.camel-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>
2017-10-23 14:23 ` Aurélien Aptel
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=mpsd16dsedg.fsf@aaptelpc.suse.de \
--to=aaptel-ibi9rg/b67k@public.gmane.org \
--cc=jlayton-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox