From: David Bremner <david@tethera.net>
To: mp39590@gmail.com, notmuch@notmuchmail.org
Subject: Re: [PATCH] configure: add --without-api-docs option
Date: Tue, 09 Aug 2016 23:05:20 +0900 [thread overview]
Message-ID: <87popijavz.fsf@maritornes.cs.unb.ca> (raw)
In-Reply-To: <20160809105246.70959-1-mp39590@gmail.com>
mp39590@gmail.com writes:
> From: Mikhail <mp39590@gmail.com>
>
> Add option to explicitly disable API man page build even if doxygen is
> available.
I'm not sure about the use case here. For some reason you want to
install some of the man pages, but not all of them?
> ---
> configure | 14 ++++++++++++--
> 1 file changed, 12 insertions(+), 2 deletions(-)
>
> diff --git a/configure b/configure
> index ae0a027..a6b6ee8 100755
> --- a/configure
> +++ b/configure
> @@ -68,6 +68,7 @@ PYTHON=${PYTHON:-}
> PREFIX=/usr/local
> LIBDIR=
> WITH_DOCS=1
> +WITH_API_DOCS=1
> WITH_EMACS=1
> WITH_BASH=1
> WITH_RUBY=1
> @@ -137,7 +138,8 @@ Some features can be disabled (--with-feature=no is equivalent to
> --without-feature) :
>
> --without-bash-completion Do not install bash completions files
> - --without-docs Do not install documentation and man pages
> + --without-docs Do not install man pages
I would say that --without-docs should imply --without-api-docs
I'm not totally convinced about the change in the description, but I
guess we can always change it back if / when we start install other
kinds of docs (e.g. html docs or info pages).
next prev parent reply other threads:[~2016-08-09 14:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-09 10:52 [PATCH] configure: add --without-api-docs option mp39590
2016-08-09 14:05 ` David Bremner [this message]
2016-08-09 14:59 ` Tomi Ollila
2016-08-10 13:02 ` mp39590
2016-08-11 6:16 ` Tomi Ollila
2016-08-11 13:02 ` David Bremner
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87popijavz.fsf@maritornes.cs.unb.ca \
--to=david@tethera.net \
--cc=mp39590@gmail.com \
--cc=notmuch@notmuchmail.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 public inbox
https://yhetil.org/notmuch.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).