unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
* bug#62751: 29.0.90; New libraries that still need to be assigned to packages
@ 2023-04-10 13:04 Jonas Bernoulli
  2023-04-10 13:30 ` Eli Zaretskii
                   ` (2 more replies)
  0 siblings, 3 replies; 45+ messages in thread
From: Jonas Bernoulli @ 2023-04-10 13:04 UTC (permalink / raw)
  To: 62751

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





^ permalink raw reply	[flat|nested] 45+ messages in thread

end of thread, other threads:[~2023-10-14 16:21 UTC | newest]

Thread overview: 45+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-04-10 13:04 bug#62751: 29.0.90; New libraries that still need to be assigned to packages Jonas Bernoulli
2023-04-10 13:30 ` Eli Zaretskii
2023-04-11 16:03 ` Michael Albinus
2023-04-11 17:16   ` Jonas Bernoulli
2023-09-05 23:49     ` Stefan Kangas
2023-09-16  9:21       ` Stefan Kangas
2023-09-16 14:23 ` Stefan Kangas
2023-09-17 22:06   ` Jonas Bernoulli via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-18  7:34     ` Stefan Kangas
2023-09-18 11:02       ` Eli Zaretskii
2023-09-18 11:10         ` Stefan Kangas
2023-09-18 11:49           ` Eli Zaretskii
2023-09-21  0:15             ` Stefan Kangas
2023-09-21  2:29               ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-21  7:26                 ` Stefan Kangas
2023-09-21 14:01                   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-22 12:36                     ` Stefan Kangas
2023-09-21  7:15               ` Eli Zaretskii
2023-09-21  7:29                 ` Stefan Kangas
2023-09-23 14:42                 ` Stefan Kangas
2023-09-24 18:07                   ` John Wiegley
2023-09-24 20:22                     ` Stefan Kangas
2023-09-24 21:05                       ` John Wiegley
2023-09-26 22:37                       ` Jonas Bernoulli via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-18 11:58       ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-21  0:06         ` Stefan Kangas
2023-09-18 15:19       ` Jonas Bernoulli via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-20 15:59         ` Jonas Bernoulli via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-24 12:29           ` Stefan Kangas
2023-10-01 13:11         ` Stefan Kangas
2023-10-01 13:56           ` Eli Zaretskii
2023-10-01 15:46             ` Stefan Kangas
2023-10-01 16:52               ` Eli Zaretskii
2023-10-01 17:46                 ` Stefan Kangas
2023-09-18 15:33       ` Jonas Bernoulli via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-21  0:04         ` Stefan Kangas
2023-09-21 21:12           ` Jonas Bernoulli via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-22 15:30             ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-23 11:35               ` Stefan Kangas
2023-10-13 23:33                 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-14  6:45                   ` Eli Zaretskii
2023-10-14 14:39                     ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-14 16:21                     ` Stefan Kangas
2023-09-19 23:12       ` Richard Stallman
2023-09-20 23:45         ` Stefan Kangas

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).