public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Maciej Barć" <xgqt@gentoo.org>
To: gentoo-dev@lists.gentoo.org, Sam James <sam@gentoo.org>
Cc: gnu-emacs@gentoo.org
Subject: Re: [gentoo-dev] [PATCH] elisp-common.eclass: fix for Emacs 29 (explicitly require autoload)
Date: Thu, 18 Aug 2022 23:28:07 +0200	[thread overview]
Message-ID: <c370e2ee-ed7e-6fa6-c6f8-9bbd211e0644@gentoo.org> (raw)
In-Reply-To: <8EEA9165-C96E-42E1-A11B-37A0F2231196@gentoo.org>


[-- Attachment #1.1.1: Type: text/plain, Size: 1398 bytes --]

> We could do it based on the Emacs version though if the eclass
> has machinery for checking that (new to poking at this area).


There are elisp-emacs-version & elisp-check-emacs-version functions.


On 8/18/22 23:25, Sam James wrote:
> 
> 
>> On 18 Aug 2022, at 21:01, Michael Orlitzky <mjo@gentoo.org> wrote:
>>
>> On Thu, 2022-08-18 at 20:18 +0100, Sam James wrote:
>>> Emacs 29's NEWS says: "The autoload.el library is now obsolete."
>>>
>>> ...
>>>
>>> 	${EMACS} ${EMACSFLAGS} \
>>> +		--eval "(require 'autoload)" \
>>> 		--eval "(setq make-backup-files nil)" \
>>> 		--eval "(setq generated-autoload-file (expand-file-name \"${f}\"))" \
>>> 		-f batch-update-autoloads "${@-.}"
>>
>> The batch-update-autoloads docstring says that it "calls 'update-
>> directory-autoloads' on the command line arguments." The function
>> update-directory-autoloads is, in turn, obsoleted in favor of loaddefs-
>> generate from loaddefs-gen.el (which replaces autoload.el).
>>
>> Can we bypass the obsolete autoload.el entirely here, instead calling
>> loaddefs-generate directly?
>>
>>
> 
> It looks like it might be new as of Emacs 29, so we'd need
> to handle older versions somehow.
> 
> We could do it based on the Emacs version though if the eclass
> has machinery for checking that (new to poking at this area).

-- 
Have a great day!

~ Maciej XGQT Barć

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 6297 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]

  reply	other threads:[~2022-08-18 21:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-18 19:18 [gentoo-dev] [PATCH] elisp-common.eclass: fix for Emacs 29 (explicitly require autoload) Sam James
2022-08-18 20:01 ` Michael Orlitzky
2022-08-18 21:25   ` Sam James
2022-08-18 21:28     ` Maciej Barć [this message]
2022-08-18 21:42       ` Sam James
2022-08-18 22:30 ` Ulrich Mueller

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=c370e2ee-ed7e-6fa6-c6f8-9bbd211e0644@gentoo.org \
    --to=xgqt@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=gnu-emacs@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