From: Ihor Radchenko <yantar92@posteo.net>
To: emacs-devel@gnu.org
Subject: pkg-autoloads.el vs. pkg-loaddefs.el
Date: Wed, 20 Mar 2024 12:56:29 +0000 [thread overview]
Message-ID: <87y1adrria.fsf@localhost> (raw)
Hello,
According to 43.1 Packaging Basics section of Elisp manual, package
autoloads are saved into pkg-autoloads.el file.
However, on master, there is also `generated-autoload-file' variable
that can override the file name where to write the autoloads. So,
pkg-autoloads.el is not always the file where autoloads are written.
Further, `elpaa-batch-generate-autoloads' in ELPA/admin/elpa-admin.el
hard-codes pkg-autoloads.el. And I got a report that in some Emacs
packages distributed through ELPA (org-mode, tramp, hyperbole), both
pkg-autoloads and pkg-loaddefs are generated.
Finally, all the libraries in Emacs core are using name-loaddefs.el.
I feel confused about where to use which name. There is apparent
inconsistency in the above facts.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next reply other threads:[~2024-03-20 12:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-20 12:56 Ihor Radchenko [this message]
2024-06-14 13:54 ` pkg-autoloads.el vs. pkg-loaddefs.el Stefan Monnier via Emacs development discussions.
2024-06-17 13:45 ` Ihor Radchenko
2024-06-17 14:04 ` Stefan Monnier
2024-06-18 16:00 ` Ihor Radchenko
2024-06-18 17:23 ` Stefan Monnier
2024-06-18 17:39 ` Ihor Radchenko
2024-06-18 19:43 ` Stefan Monnier
2024-06-18 20:03 ` Ihor Radchenko
2024-06-18 20:12 ` Stefan Monnier
2024-06-19 15:32 ` Ihor Radchenko
2024-06-19 15:58 ` Stefan Monnier
2024-06-19 16:22 ` Ihor Radchenko
2024-06-19 20:35 ` Stefan Monnier
2024-06-20 5:01 ` Eli Zaretskii
2024-07-28 13:52 ` Ihor Radchenko
2024-08-14 0:31 ` Stefan Monnier
2024-08-14 5:43 ` Eli Zaretskii
2024-06-20 15:33 ` Ihor Radchenko
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=87y1adrria.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-devel@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).