From: Noam Postavsky <npostavs@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Glenn Morris <rgm@gnu.org>, Eli Zaretskii <eliz@gnu.org>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: master 7b1026c: * make-dist: Don't fail if building --without-makeinfo.
Date: Sat, 5 May 2018 10:41:42 -0400 [thread overview]
Message-ID: <CAM-tV-9jd3Q1iOFBEFjvfh7_fgRHuhU-USXHo8M_yVO_zgkmnw@mail.gmail.com> (raw)
In-Reply-To: <47942442-bed0-8e11-0394-89877f577b23@cs.ucla.edu>
On 5 May 2018 at 02:53, Paul Eggert <eggert@cs.ucla.edu> wrote:
> Eli Zaretskii wrote:
>>>
>>> So would adding a --no-info argument (as in the attached) be okay?
>>
>> I think it would. But maybe it will make even more sense to try
>> building the Info files, and only make the failure to do it non-fatal
>> with that switch specified, WDYT?
>
> Unless you specify --no-update, make-dist already tries to build the info
> files. If that fails make-dist goes ahead anyway; perhaps it shouldn't.
For the automated testing builds, I pass '--tests --no-update
--no-changelog' to make-dist.
So the failure I want to avoid is just the part where the info files
get hard-linked into the dist directory (because the test env comes
without makeinfo).
next prev parent reply other threads:[~2018-05-05 14:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180504121034.26106.19654@vcs0.savannah.gnu.org>
[not found] ` <20180504121035.E624020E93@vcs0.savannah.gnu.org>
2018-05-04 15:48 ` master 7b1026c: * make-dist: Don't fail if building --without-makeinfo Glenn Morris
2018-05-04 17:36 ` Eli Zaretskii
2018-05-05 2:15 ` Noam Postavsky
2018-05-05 6:46 ` Eli Zaretskii
2018-05-05 6:53 ` Paul Eggert
2018-05-05 14:41 ` Noam Postavsky [this message]
2018-05-05 6:56 ` Paul Eggert
2018-05-05 14:47 ` Noam Postavsky
2018-05-05 15:34 ` Eli Zaretskii
2018-05-05 17:33 ` Paul Eggert
2018-05-13 15:05 ` Noam Postavsky
2018-05-20 13:48 ` Noam Postavsky
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAM-tV-9jd3Q1iOFBEFjvfh7_fgRHuhU-USXHo8M_yVO_zgkmnw@mail.gmail.com \
--to=npostavs@gmail.com \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rgm@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.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).