--- Begin Message ---
|
Subject: |
29.0.90; New libraries that still need to be assigned to packages |
|
Date: |
Mon, 10 Apr 2023 15:04:53 +0200 |
Hello,
Some new libraries still need to be assigned to a package in
`package--builtins'.
In some cases it seems clear to me, or at least likely, that we forgot
to declare the package when adding the new library. I.e., that treating
them as packages in their own right, was not intentional, but the result
of that being the fallback behavior when no package is explicitly
specified.
1. ietf-drums-date.el (summary: "parse time/date for ietf-drums.el"),
should be part of ietf-drums.
3. package-vc.el should probably be treated as a package separate
from Package, to make it easier to distribute Package on GNU ELPA.
4. All, or most, of the *-ts-mode.el probably should be treated as
separate packages.
5. c-ts-common.el should probably not be a separate package. Maybe it
should be part of c-ts-mode, or maybe even all the *-ts-mode.el, that
depend on this library, should be part of a single c-ts-mode?
The following packages are also listed separately in package--builtins,
but I tend to think that is not intentional.
part of?:
6. lisp/keymap.el emacs
7. lisp/emacs-lisp/oclosure.el emacs
8. lisp/net/tramp-container.el tramp
9. It seems a bit excessive to consider each use-package*.el a separate
package. Maybe they should all be part of a single use-package
package. An entry in finder--builtins-alist should be used to
accomplish that.
10. All the lisp/net/eudc*.el should probably be part of a single eudc
package.
11. All the lisp/image/image-dired*.el should probably be part of a
single image-dired package.
Maybe we should stop falling though to assign a new library to its own
separate package, if nothing else is specified explicitly? It is of
course nice not having to either add a "Package" library header or a
finder--builtins-alist entry, but it also makes it easy to forget to
explicitly specify the package when doing that would be necessary.
Speaking of finder--builtins-alist, what about adding these entries?:
("leim" . emacs)
("obsolete" . emacs)
Cheers,
Jonas
--- End Message ---
--- Begin Message ---
|
Subject: |
Re: bug#62751: 29.0.90; New libraries that still need to be assigned to packages |
|
Date: |
Sun, 24 Sep 2023 13:22:57 -0700 |
Version: 30.1
John Wiegley <johnw@gnu.org> writes:
>> Should bind-key.el be in lisp/? lisp/emacs-lisp/?
>
> I would put it in lisp/, since it relates to Emacs functionality rather than
> the Emacs Lisp programming language in particular.
Now done on master (commit 947409d408e). I think that's the last of the
outstanding issues in this bug, so I'm closing it with this message.
--- End Message ---