| Age | Commit message (Collapse) | Author |
|---|
|
An error was fixed and code was cleaned up.
|
|
This release adds a translation, improves animation and declares
compatibility to gnome-shell version 41.
|
|
This release updates translations and (re-)adds features, most notably
per-monitor window switching.
|
|
In addition to now being only compatible to gnome-shell version 40, a
new translation was added.
|
|
Since GNOME (3.)40, the former first component of the version number is
dropped. [1] Functions that input or output version numbers are now
compatible with both schemes, making it possible to even manage
extensions that declare compatible versions ranging from before to after
shell version (3.)40.
[1]: https://discourse.gnome.org/t/new-gnome-versioning-scheme/4235
|
|
Certain versions of the gnome-shell binary refuse to run as root, only
outputting an error message. Not even the --version option is parsed.
As the package function runs under FakeRoot, it looks exactly like that
to the program. FakeRoot works by modifying the LD_LIBRARY_PATH and
LD_PRELOAD. By clearing the library to preload, usual function is
restored.
This can be reasonably be considered safe, as the program is only run
with a parameter to output its version number and exit, not making any
modification or communications to or with the rest of the system.
|
|
The extension is now compatible to gnome-shell version 3.38.
Compatibility for some older versions was removed, in turn.
|
|
In addition to a new translation, the extension is now compatible to
gnome-shell version 3.36.
|
|
Since version 3.30.1-1, gnome-shell has an epoch. [1] Incorporating it
in the dependency limits make version comparisons work correctly again.
This is especially important for upper bounds for which it makes
installation possible again.
[1]: https://github.com/archlinux/svntogit-packages/commit/5ef13f847cae14961ace4d15210bc55623b074cb
|
|
The commit actually marking the extension as compatible was missing from
the last release and is now included.
|
|
Since Pacman version 5.2.0 makepkg exits whenever any command in a
pkgver function returns a non-zero exit code. A recent correction from
the git-makepkg-templates [1] adapts to this, restoring correct
processing of the PKGBUILD.
As this concern only the build process, not changing any of the
resulting package content, the pkgrel is kept constant, to avoid
triggering any unnecessary rebuild.
[1]: https://github.com/dffischer/git-makepkg-templates/commit/d91fca9b16dd03bc0bf924dbd95dd24b06e232fe
|
|
The extension is now compatible with the gnome-shell version 3.34.
|
|
Besides compatibility with the current gnome-shell version 3.32, this
update also brings interoperability with the optistatus extension. [1]
[1]: https://extensions.gnome.org/extension/710/optistatus/
|
|
Some errors were silenced. To do so, this update drops backwards
compatibility to older gnome-shell versions.
|
|
A bug with the timeline switcher, introduced in the last compatibility
update, was fixed.
|
|
Apart from translation and documentation updates, compatibility with
gnome-shell version 3.30 arrived.
|
|
The new gnome-shell version 3.28 is now supported.
|
|
The recently released gnome-shell version 3.26 is now supported.
|
|
Newer Cinnamon and GNOME Shell versions are now supported.
|
|
|
|
Some extensions authors introduce build steps required before
installing. Their execution normally produces a completed variant of the
extension code in a subdirectory, difficult to tell apart from the
original source. The find condition introduced herein proves the process
against such cases to come. It always chooses the files created last,
ensuring that a build which occurred after mere unpacking will always
take precedence.
|
|
Although the version number was not incremented compatibility updates
should be shipped out to not hinder gnome-shell updates.
|
|
The git-makepkg-templates switched to dynamic adaptation to integrity
checks chosen in makepkg.conf. [1] The default checksums chosen reflect
recommendations from the Arch Linux Wiki and manual pages. [2]
[1]: https://github.com/dffischer/git-makepkg-templates/commit/e84d04b
[2]: https://aur.archlinux.org/cgit/aur.git/commit/?h=git-makepkg-templates-git&id=c2ccaaa
|
|
According to the Arch Packaging Standards [1], lines in a PKGBUILD
should be no longer than 100 characters.
This does not change the contents of the built package, so the pkgver
stays unchanged.
[1]: https://wiki.archlinux.org/index.php/Arch_packaging_standards
|
|
Since commit 5e7b3d6 [1], the repository contains a partial variant of
the extension, which may be falsely located when searching only for the
metadata.json. As an extension consists of both the metadata description
and a JavaScript entry point always named extension.js, searching for
both only matches final composed extension.
This does not change the contents of the built package, so the pkgver
stays unchanged.
[1]: https://github.com/dmo60/CoverflowAltTab/commit/5e7b3d6
|
|
Although the project did not yet release a version containing commit
5015da5 [1], it is worth shipping out as it improves compatibility with
all extensions modifying the legacy tray or the dock, e.g. the popular
dash-to-dock.
[1]: https://github.com/dmo60/CoverflowAltTab/commit/5015da5
|
|
Comparing the minor version to a string of minor and major will never
succeed.
Originally, a restriction on the current shell version was omitted for
historical reasons - most packages did so when dependencies were defined
manually. This now turns into a concious decision to
- permit the usage of the extension in instable gnome-shell versions -
the ones with odd minor version numbers - where incompatibilities are
introduced gradually.
- ease the transition from one stable gnome-shell version - the ones
with even minor version numbers - to the next. In an ideal world, all
extensions should have been updates before the update hits the
repositories. But as Arch is quite more on the edge than developers of
some of the extensions, this is not the case more often than not.
|
|
This introduces compatibility for gnome-shell version 3.20.
|
|
Unbelievably, also traditional tools like grep are regularly updated
still today. Version 2.24 forbid the combination of some features with
the -z option. This was exactly what was exploited here to make grep
ignore newlines so they would not interrupt JSON dissection. More
information about the change can be found at the bottom of the
respective release notes. [1]
Fixing it costs an invocation of tr to remove the bothersome newlines.
Because the files are read within "find -exec" where input redirection
is not readily possible, cat has to be invoked to start the pipeline.
The grep script got only a tiny bit simpler by adhering to the new
restriction and leaving newlines to tr.
Thanks to AUR users jmauss, Asher256 and vinadoros for pointing to the
critical line.
[1]: http://savannah.gnu.org/forum/forum.php?forum_id=8477
|
|
This reverts "add mksrcinfo header".
The .SRCINFO is now generated by "makepkg --printsrcinfo" which does no
longer include any header since commit f63854f [1], released with pacman
version 5.0.1.
[1]: https://projects.archlinux.org/pacman.git/commit/?id=f63854fa96f658ca5bdf2c21a1cd33cf4e3fbdbd
|
|
Other packages usually depend on the package without any -git suffix.
This makes it possible to als satisfy these dependency requirements when
they target specific versions or version ranges.
|
|
The new version of mksrcinfo released with the recent update to
pkgbuild-introspection adds a header to all .SRCINFO files.
|
|
Apart from translation updates, this introduces compatibility for
gnome-shell version 3.18.
|
|
|
|
This package is now maintained as part of the collection of
gnome-shell-extensions and related templates on GitHub.
<https://github.com/dffischer/gnome-shell-extensions>
|
|
|
|
|