On 06/07/2023 06:02, Nicholas D Steeves wrote:
"H.-Dirk Schmitt" writes:
A „clean solution“ should avoid duplicated distribution of the same
functionality – especially if one „shadows“ the other.
Can upstream be convinced of this „clean solution“?
If I remember correctly, Richard Stallman considers Org mode as an
important part of Emacs. On the other hand there are users who prefer to
have Org newer than built-in version, fortunately it is developed in a
separate repository.
I am unsure that it is reasonable to split Emacs Debian package into a
squad of smaller ones if an elpa-* counterpart is available. Perhaps it
is easier to review elpa-* packages after packaging of new Emacs
versions. I do not see much sense in painstakingly avoiding load shadowing.
For example a script that parses our Emacs' built-in
version, and that files release critical bugs against an elpa-foo
package when it's older than the Emacs built-in version.
package.el is created for interactive usage (`list-packages'), so the
script will have to rely on internal variable and functions. When the
package source file is known, `lm-header' may be used to obtain specific
fields. It is doable, but unlikely straightforward.
P.S. Thanks for packaging of Org-9.6. I did not notice the experimental
package.
