Control: tags -1 moreinfo Hi,
I haven't thought this trough, but it immediately triggered questions: On 08-05-2023 20:46, Sean Whitton wrote:
A number of Emacs addon packages which have their own source packages also have versions shipped in src:emacs's binary packages (upstream calls these "core" ELPA packages). We have them separately packaged mainly because of how Emacs's release cadence does not line up well with Debian's. So having them separately packaged means we can ship newer versions of the addons even if we're having to ship an older version of Emacs. This scheme requires, however, that we don't allow it to ever transpire that the version in src:emacs is newer than the version in the separate source package, because Emacs prefers to load the separately installed version to the bundled version, even when the latter has a higher version number. Unfortunately, src:org-mode is undermaintained, and so precisely that situation has arisen in bookworm. We can resolve this by temporarily changing bin:elpa-org as described above, for bookworm, and then populating it again after the freeze.
What's the plan for the future? Is this a one-off exercise or do you intent to pull this trick more often?
IIRC other ecosystems (like ruby) have the main package also (versioned) Provides these add-ons, such that when packages Depend on it, the main package can provide it without needing the add-on. That way, you could prevent shipping the package in a stable release when it's behind and have a newer version if it's available. Has such a scheme been considered? If yes, what's the drawback?
Paul
OpenPGP_signature
Description: OpenPGP digital signature