GNOME Bugzilla – Bug 639255
Introduce versioning in the extension system
Last modified: 2011-01-12 21:07:20 UTC
As discussed on the mailing list, since the API is not stable we need extensions to declare which version of the shell they support.
Created attachment 178091 [details] [review] Propagate version to Javascript files Add an entry in config.js.in for PACKAGE_VERSION and GJS_VERSION, to be used by the notification daemon and in the future by the extension system.
Created attachment 178092 [details] [review] ExtensionSystem: introduce versioning Require that all extensions have a "shell-version" property in their metadata, which is an array of supported Shell versions. Extensions can target a specific version triple or an entire stable version. Optionally, they can also require a specific GJS version, to ensure compatibility.
Review of attachment 178091 [details] [review]: Looks good!
Review of attachment 178092 [details] [review]: Looks good in general. Why the micro version if we don't use it?
(In reply to comment #4) > Review of attachment 178092 [details] [review]: > > Looks good in general. Why the micro version if we don't use it? I've seen micro versions in other packages in the past, I don't want to break extensions because someone made a mistake in releasing, or because of a small crasher (small in the sense of the fix needed).
Fixed now, thanks!