| Age | Commit message (Collapse) | Author |
|---|
|
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.
|
|
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
|
|
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.
|
|
This does not switch the source back to the original upstream, which did
not merge the pull request mentioned in the last commit "source from
fork" modifying this package, which caused the digression. Instead,
another fork was chosen, because it seems to be the most active, already
having pulled together multiple other forks, one of them the
aforementioned. Its maintainer also took over the closely related window
buttons extension.
|
|
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.
|
|
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
|
|
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.
|
|
This introduces shell version 3.18 compatibility. A pull request [1] is
already filed, but not merged a few weeks since, so compatibility is
shipped out via the fork until upstream merges.
[1]: https://github.com/wilfm/GnomeExtensionMaximusTwo/pull/41
|
|
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.
|
|
The original maintainer greatly updated the code, fixed many bugs and
made it officially compatible with the latest shell version. So the
package can use this source instead of a fork again.
|
|
|
|
|