On Tue, 28 Nov 2023 at 02:47, Maxime Devos <[email protected]> wrote:
>> Once builtin, the code of a package distributed with GNU Emacs is >> maintained by Emacs maintainers and fully part of GNU Emacs. > > Yes, and? How does being fully part of GNU Emacs and being maintained > by Emacs maintainers make it any less bundling? There is more to > development than maintenance. Please read GNU Emacs documentation and how GNU Emacs is developed. I have tried to do my best for pointing you some links. If these are not enough, you should dig by your own. Maybe ask on emacs-devel mailing list how the GNU Emacs development process works. > If making emacs-mnimal more minimal is too complicated, don't do it > then, just replace the bundled copy with an up-to-date (source) version, > as I proposed previously. This is *not* the GNU Emacs release model. GNU Emacs version X.Y *is* all the exact same files as the ones stored in Savannah. If you want to replace the file /gnu/store/…-emacs-X.Y/share/emacs/X.Y/lisp/transient.el.gz by something else, you need to package that exact file. Therefore, your proposal would imply to have two packages: + emacs-transient-next following development of transient.el – this development happens outside Savannah. Please note for other builtin packages, this development happens inside the Emacs repository located in Savannah. + emacs-transient providing the exact same version as the builtin one tracked in the GNU Emacs release X.Y branch located in Savannah. Again, transient.el is not bundled. It is a builtin package which means it is fully part of GNU Emacs. Being developed outside Savannah does not make it bundled. Regards, simon
