Hello:
The version in the metadata.json is managed by the ego website.
See https://wiki.gnome.org/Projects/GnomeShell/Extensions
The version is not required when uploading an extension to the website.
The version is determined when an extension is uploaded. The version
is
calculated by the increment of the version of the last upload of the
extension.
When a user visits the website with a compatible browser a check of
each
installed extension is performed. If a newer version compatible with
the
user's shell version is available the extension is flagged on the
installed
extensions page. If the user has a string in the version field of the
metadata.json the check does not work.
My make files replace the date and the git commit tag at the end of the
extension's README.txt when the zip file is created. That seems to be
the information you want to know as the zip file is used to install
the extension.
Regards,
Norman
On Mon, 2016-01-18 at 03:34 +0100, Thomas DEBESSE wrote:
> Hi, I'm modifying a gnome shell extension, is the version number in
> metadata.json can be a string containing alphabetic character ? it
> looks like all extensions I have use a decimal number, but it's not
> very convenient…
>
> I want to use a version number based on git revision (like
> "1.0~git160117062634.d1c3b60" for example), so my makefile can just
> write down a new version number at build time.
>
> --
> Thomas DEBESSE
> _______________________________________________
> gnome-shell-list mailing list
> gnome-shell-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/gnome-shell-list
_______________________________________________
gnome-shell-list mailing list
gnome-shell-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-shell-list
