From: ludo@gnu.org (Ludovic Courtès)
To: Mathieu Lirzin <mthl@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 0/4] Build man pages in $(srcdir).
Date: Sat, 19 Mar 2016 22:28:36 +0100 [thread overview]
Message-ID: <878u1ef98b.fsf@gnu.org> (raw)
In-Reply-To: <1458404286-10448-1-git-send-email-mthl@gnu.org> (Mathieu Lirzin's message of "Sat, 19 Mar 2016 17:18:02 +0100")
Mathieu Lirzin <mthl@gnu.org> skribis:
> Anyway, inspired by what is done by Automake for info manuals I have tried to
> build man pages in $(srcdir), which is fixing the issue too. The bonus is
> that now all the documentation is consistently built in $(srcdir) and that we
> avoid adding another "case $? ..." trick.
This sounds reasonable (in fact I wonder why we were not doing it
already given that things are supposed to live in $(srcdir)).
Did you confirm that ‘make distcheck’ passes after that, and that
‘help2man’ is not invoked when building from a tarball?
Thank you!
Ludo’.
next prev parent reply other threads:[~2016-03-19 21:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-19 16:18 [PATCH 0/4] Build man pages in $(srcdir) Mathieu Lirzin
2016-03-19 16:18 ` [PATCH 1/4] Revert "build: Do not remake doc/guix.1." Mathieu Lirzin
2016-03-19 21:29 ` Ludovic Courtès
2016-03-19 16:18 ` [PATCH 2/4] build: Make 'guix' man page depend on scripts/guix.in Mathieu Lirzin
2016-03-19 21:31 ` Ludovic Courtès
2016-03-19 16:18 ` [PATCH 3/4] build: Build man pages in $(srcdir) Mathieu Lirzin
2016-03-19 21:31 ` Ludovic Courtès
2016-03-19 16:18 ` [PATCH 4/4] build: Rewrite comments for man pages Mathieu Lirzin
2016-03-19 21:32 ` Ludovic Courtès
2016-03-19 21:28 ` Ludovic Courtès [this message]
2016-03-19 21:33 ` [PATCH 0/4] Build man pages in $(srcdir) Ludovic Courtès
2016-03-19 22:50 ` Mathieu Lirzin
2016-03-20 21:09 ` Ludovic Courtès
2016-03-20 23:03 ` Mathieu Lirzin
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=878u1ef98b.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=mthl@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.