From: Glenn Morris <rgm@gnu.org>
To: 46837@debbugs.gnu.org
Subject: bug#46837: Makefile dependencies for info files
Date: Sun, 28 Feb 2021 18:39:40 -0500 [thread overview]
Message-ID: <wrr1kz3goz.fsf@fencepost.gnu.org> (raw)
Package: emacs
Version: 28.0.50
Tags: help
I suspect that the Makefile dependencies for info files could be
incomplete as of 4825ea3c5d. The symptoms would be info related errors
in parallel builds, and missing files in info/dir.
I would appreciate it if someone would review it.
It's not made any easier by:
1) Catering for systems without makeinfo - I would suggest dropping this.
2) All the nested phony info rules.
Other possible improvements:
1) build-aux/make-info-dir to parse .org sources (for texinfo_dir_category)
in preference to .texi ones if the former exist.
2) Replace dependency on info files with one on generated texi files,
where it makes sense.
(Personally I find this quite a PITA, both from the point of view of
Makefile rules, and from now needing to know two markup syntaxes to
maintain Emacs's manuals. End of complaint.)
next reply other threads:[~2021-02-28 23:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-28 23:39 Glenn Morris [this message]
2021-03-01 16:47 ` bug#46837: Makefile dependencies for info files Eli Zaretskii
2021-03-04 18:53 ` Glenn Morris
2021-03-04 19:22 ` Eli Zaretskii
2021-03-04 19:00 ` Glenn Morris
2021-03-05 4:45 ` Glenn Morris
2021-03-05 7:31 ` Eli Zaretskii
2021-03-05 19:23 ` Glenn Morris
2021-03-05 19:34 ` Stefan Kangas
2021-03-07 10:52 ` Michael Albinus
2021-03-07 17:14 ` Glenn Morris
2021-03-07 17:22 ` Michael Albinus
2021-03-07 17:33 ` Glenn Morris
2021-03-07 17:49 ` Michael Albinus
2021-03-07 17:38 ` Glenn Morris
2021-03-08 17:51 ` Glenn Morris
2021-03-08 17:58 ` Michael Albinus
2021-03-05 20:12 ` Eli Zaretskii
2021-03-06 17:38 ` Glenn Morris
2021-03-06 18:12 ` Eli Zaretskii
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=wrr1kz3goz.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=46837@debbugs.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).