Commit Graph

8 Commits

Author SHA1 Message Date
Giovanni Campagna dfca68062c build system: add additional automatic metadata
Add "gettext-domain", "extension-id" (containing the base part of the
UUID) and "gschemabase" (which, combined with "extension-id", gives
the GSettings schema) to metadata.json, autogenerated by the build
system.
2012-02-08 18:00:56 +01:00
Giovanni Campagna 10aec91ebb Bump version to 3.3.2
To go with GNOME Shell 3.3.2, bump configure.ac, update NEWS and
mark all extensions to be only compatible with the unstable release.
2011-11-22 09:11:46 +01:00
Giovanni Campagna 7a6777f703 Remove all references to localedir from metadata.json
It is not used anymore, now that translations are bundled with
the extension. Also, in the zip files it ended up with my home
folder, which is not nice.
2011-11-20 00:40:20 +01:00
Giovanni Campagna 00bb650c6c Add 3.2 tags to supported version
This is the stable release, so we support all of GNOME Shell
stable cycle without updates.
(As said earlier, dock and alternate-tab have issues, so they're
not marked 3.2 but just 3.2.0)
2011-10-03 17:33:28 +01:00
Giovanni Campagna 0ce994ba46 Revert "Mark extensions that require only public API"
This reverts commit 6cd9530862, and
reopens development againts GNOME Shell master. Time for 3.2!
2011-04-26 01:17:23 +02:00
Giovanni Campagna 6cd9530862 Mark extensions that require only public API
Extensions that use public Shell API are expected to work for all
stable 3.0 releases, so we skip setting the minor version. (This
means that they'll work in 3.0.0 and 3.0.1 without rebuilding).
Notably absent are auto-move-windows and windowsNavigator, that
hook deep into Shell code and could be broken by next minor release.
2011-04-05 16:42:48 +02:00
Giovanni Campagna fbbe5ba764 Add url property in the metadata
GNOME Shell emits a warning when "url" is absent in metadata.json,
adding it costs nothing. Links to the GIT repository because I
found no better page to reference.
2011-02-26 16:41:52 +01:00
Giovanni Campagna aaf2057725 Build system: generate metadata.json
Instead of hardcoding metadata.json, generate it from .in files,
adding installation prefixes, current target version and configured
uuid.
2011-02-07 22:52:42 +01:00