control: tag -1 - moreinfo Hello,
Thanks for looking. On Mon 08 May 2023 at 09:33PM +02, Paul Gevers wrote: > What's the plan for the future? Is this a one-off exercise or do you > intent to pull this trick more often? We don't have a real plan for the future, aside from trying to keep these packages up-to-date. It would be good to have a script that we could run right after uploading new versions of Emacs, that would find addons that are now behind. So, we'd like it to be one-off, but due to limited manpower on the team, I can't pretend that it couldn't happen again. Ultimately I think that the correct fix is for Emacs to learn to load the version of the package that has the highest version number. So, I think this is, at bottom, an upstream limitation. But I might be wrong about that. > 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? We haven't considered it. It would be a case of writing a script to generate the required Provides values from the Emacs source. -- Sean Whitton
signature.asc
Description: PGP signature
