Hello, On Thu 27 Feb 2025 at 04:10pm -08, Xiyue Deng wrote:
> I have a quick and dirty script (attached) trying to find all packages > that may have a corresponding builtin package (it may have missed a few > though), and the result is the following: > > ,---- > | elpa-xref > | elpa-which-key > | elpa-use-package > | elpa-transient > | elpa-seq > | elpa-project > | elpa-org > | elpa-let-alist > | elpa-faceup > | elpa-eglot > | elpa-editorconfig > | elpa-compat > | elpa-bind-key > `---- > > Removing what Sean already mentioned, adding elpa-peg which is currently > in the NEW queue, we have the following (sorted): > > ,---- > | elpa-bind-key > | elpa-compat > | elpa-editorconfig > | elpa-eglot > | elpa-faceup > | elpa-peg > | elpa-use-package > | elpa-which-key > `---- > > According to etc/NEWS, editorconfig, which-key, peg, and compat are > newly added in 30.1. Of those 8, editorconfig, which-key, eglot, > bind-key, faceup, and use-package has no reverse dependency. elpa-peg > was introduced for emacs-pg-el with the new upstream, and I guess > elpa-compat will still be regularly updated. Maybe the 6 packages > without rdepends can also be candidates to be kept from Trixie (or even > RM)? Thanks. Well, it's case-by-case. It depends on how much development they are seeing, I think. compat-el we probably want to keep. Its purpose is to allow other addons to use features that are newer than the major version of Emacs we have. It's useless when its major version is in sync with Emacs's, but that's not always going to be the case. elpa-bind-key and elpa-use-package go together. Might people would want newer features? Are they getting new features? eglot, editorconfig, peg, faceup, IHNI. What we want to imagine is the situation where a new version of Emacs comes out during our freeze, so Debian is either one or two major releases behind for at least two years. What might we want to ensure we can ship newer version of, in that case? Really we want to be aiming to RM or keep in trixie. My "keep out of trixie" bugs are meant to be a step towards removal. It's not good for packages to disappear in one stable release and then reappear in the next. -- Sean Whitton
signature.asc
Description: PGP signature
