From: "Ulrich Müller" <ulm@gentoo.org>
To: Sam James <sam@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH] elisp.eclass: Call makeinfo with --no-split option
Date: Fri, 27 Dec 2024 10:36:04 +0100 [thread overview]
Message-ID: <uzfkhjwmz@gentoo.org> (raw)
In-Reply-To: <878qs1tuq2.fsf@gentoo.org> (Sam James's message of "Fri, 27 Dec 2024 08:07:17 +0000")
[-- Attachment #1: Type: text/plain, Size: 745 bytes --]
>>>>> On Fri, 27 Dec 2024, Sam James wrote:
> (Why?)
By default, makeinfo will split large output files into smaller
subfiles. Although this doesn't currently happen for any package,
it might happen in future, and it would break some assumptions.
The threshold for splitting is 300 kB, and we have at least three
packages with larger info files. The reason they don't break is that
they use the upstream Makefile rather than the eclass function.
>> --- a/eclass/elisp.eclass
>> +++ b/eclass/elisp.eclass
>> @@ -139,7 +139,7 @@ elisp_src_configure() { :; }
>> elisp_src_compile() {
>> elisp-compile *.el
>> if [[ -n ${ELISP_TEXINFO} ]]; then
>> - makeinfo ${ELISP_TEXINFO} || die
>> + makeinfo --no-split ${ELISP_TEXINFO} || die
>> fi
>> }
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 507 bytes --]
prev parent reply other threads:[~2024-12-27 9:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-26 12:04 [gentoo-dev] [PATCH] elisp.eclass: Call makeinfo with --no-split option Ulrich Müller
2024-12-27 8:07 ` Sam James
2024-12-27 9:36 ` Ulrich Müller [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=uzfkhjwmz@gentoo.org \
--to=ulm@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=sam@gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox