| Age | Commit message (Collapse) | Author |
|---|
|
Apart from translation updates and improvements in configuration
options, the upcoming gnome-shell version 3.22 is already supported.
|
|
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
|
|
A much requested feature similarly present in other extensions yields
the possibility to incorporate dash-to-dock in a workspace-isolated
workflow. This is a significant update users of the git variant of this
package may appreciate, so it is shipped out even without a release by
the upstream project. Aside, a feature update cannot hurt in the dry
spell between biannual GNOME updates.
|
|
According to the Arch Packaging Standards [1], lines in a PKGBUILD
should be no longer than 100 characters and package descriptions should
cap at 80.
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
|
|
As an extension consists of both the metadata description and a
JavaScript entry point always named extension.js, searching for both
hardens the locating process against changes to the directory structure.
This does not change the contents of the built package, so the pkgver
stays unchanged.
|
|
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.
|
|
Apart from translation updates, the intellihide machinery has been
optimized. The extension can now also be active with full screen windows
and supports the upcoming gnome-shell version 3.20.
Fortunately, the same dash-to-dock release applies to gnome-shell 3.18
and 3.20 as well. This provides the hopeful perspective that transition
will be effortless when the next stable shell version hits the Arch
Linux repositories.
|
|
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
|
|
The original description from GitHub is quite long, so eliminating the
first few words about how it is an extension for gnome-shell does not
hurt as this fact is already expressed in the package name.
|
|
This injects the package version information into the metadata.json,
instead of just defaulting to the current commit hash, which is part of
the pkgver anyway.
|
|
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.
|
|
|
|
Meanwhile, the bug in librsvg propagated upstream. [1]
Though it has not been fixed as of now, the maintainer of the extension
cared for the issue as well [2] and was so kind to rework the image not
to trigger it to begin with [3]. So there is no need to patch the image
any longer and the respective commit "patch up unreadable image" can be
reverted, bringing this package as close to upstream as it has been.
This change does not increase the pkgrel as there is no functional
change to be shipped out. Already installed packages will continue to
work without the need of an update.
[1]: https://bugzilla.gnome.org/show_bug.cgi?id=759084
[2]: https://github.com/micheleg/dash-to-dock/issues/262
[3]: https://github.com/micheleg/dash-to-dock/commit/8a7e74e
|
|
The imagemagick package contains the convert program needed for the
interim fix.
|
|
Due to a bug with librsvg[1] GTK is unable to process the image
logo.svg. As ImageMagic still can handle it without any hiccups, it can
be converted to a PNG before GTK ever sees it until the bug is fixed.
[1]: https://bugs.archlinux.org/index.php?do=details&task_id=47245
|
|
Among with a few minor changes, it provides compatibility with soon to
be released shell version 3.18.
|
|
Sorting the template inclusion by the order of their package functions
being called showed a bug swallowing dependencies. Misusing the indexed
array of dependencies placed the element assigned by a key in first
position always overwriting an already present element. Using a symbolic
number makes it work fine as long as it is ensured that this number is
greater than the number of dependencies, which should be fairly probable
with 125.
|
|
|
|
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>
|
|
|
|
|