From: Lars Ingebrigtsen <larsi@gnus.org>
To: Jonas Bernoulli <jonas@bernoul.li>
Cc: 55388@debbugs.gnu.org
Subject: bug#55388: 28.1; New libraries that neither belong to a package nor provide a feature
Date: Fri, 13 May 2022 14:45:01 +0200 [thread overview]
Message-ID: <87ilq9vbxu.fsf@gnus.org> (raw)
In-Reply-To: <8735hetx8s.fsf@bernoul.li> (Jonas Bernoulli's message of "Thu, 12 May 2022 20:35:31 +0200")
Jonas Bernoulli <jonas@bernoul.li> writes:
> "lisp/emacs-lisp/shorthands.el" doesn't provide a feature and lacks
> a "Package" library header. I think "Package: emacs" should be added.
>
> Like other files in that directory "lisp/leim/quail/cham.el" neither
> provides a feature nor is it explicitly made part of a package. Would
> it make sense to add ("leim" . emacs) to `finder--builtins-alist'?
Are all .el files supposed to have either a Package: header or a
`provides' these days? I wasn't aware of that...
Hm... I see that Chong did something like that with all the preloaded
.el files in bd78fa1d544, so I guess that's true?
> Maybe another such entry should be added for the "obsolete" directory?
>
> Unlike other "epa-*" libraries, "lisp/epa-ks.el" isn't made part of
> the "epa" package and fails to provide a feature.
I think it's separate thing, but it should have a provides, so I've now
added that.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-05-13 12:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-12 18:35 bug#55388: 28.1; New libraries that neither belong to a package nor provide a feature Jonas Bernoulli
2022-05-13 12:45 ` Lars Ingebrigtsen [this message]
2022-06-28 21:37 ` Stefan Kangas
2022-06-29 9:58 ` Lars Ingebrigtsen
2022-06-29 11:35 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-30 8:58 ` Lars Ingebrigtsen
2023-09-17 23:15 ` Stefan Kangas
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=87ilq9vbxu.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=55388@debbugs.gnu.org \
--cc=jonas@bernoul.li \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.