From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org, brobecker@adacore.com,
simark@simark.ca, fejfighter@gmail.com
Subject: Re: [PATCH] Add epub output for documentation
Date: Wed, 09 Nov 2022 18:48:35 +0200 [thread overview]
Message-ID: <83mt90t6os.fsf@gnu.org> (raw)
In-Reply-To: <87leok2ko6.fsf@tromey.com> (message from Tom Tromey on Wed, 09 Nov 2022 08:48:41 -0700)
> From: Tom Tromey <tom@tromey.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, Joel Brobecker <brobecker@adacore.com>,
> Simon Marchi <simark@simark.ca>, fejfighter@gmail.com
> Date: Wed, 09 Nov 2022 08:48:41 -0700
>
> Simon> "make install" only installs the man pages and the info version of the
> Simon> manual. The pdf or html versions of the manual are only installed with
> Simon> explicit "install-pdf" and "install-html" rules. So I presume that epub
> Simon> would be the same as pdf and html.
>
> I think so too. Is there a typical GNU directory for where exactly
> these should be installed?
No, we are on our own.
I think it would be good to tell the Texinfo maintainers to start
thinking about a standard directory for EPUB format, because more and
more projects will bump into this issue.
prev parent reply other threads:[~2022-11-09 16:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 7:54 Fejfighter
2022-11-09 12:38 ` Eli Zaretskii
2022-11-09 13:21 ` Simon Marchi
2022-11-09 13:22 ` Eli Zaretskii
2022-11-09 13:41 ` Simon Marchi
2022-11-09 13:44 ` Eli Zaretskii
2022-11-09 13:48 ` Simon Marchi
2022-11-09 15:48 ` Tom Tromey
2022-11-09 16:15 ` Simon Marchi
2022-11-09 16:53 ` Mike Frysinger
2022-11-09 17:09 ` Eli Zaretskii
2022-11-09 16:48 ` Eli Zaretskii [this message]
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=83mt90t6os.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=fejfighter@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
--cc=tom@tromey.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).