Package Details: gnome-shell-extension-tilingshell 17.2-1

Git Clone URL: https://aur.archlinux.org/gnome-shell-extension-tilingshell.git (read-only, click to copy)
Package Base: gnome-shell-extension-tilingshell
Description: Extend GNOME Shell with advanced tiling window management.
Upstream URL: https://github.com/domferr/tilingshell
Licenses: GPL-2.0-or-later
Submitter: yochananmarqos
Maintainer: yochananmarqos
Last Packager: yochananmarqos
Votes: 2
Popularity: 0.002385
First Submitted: 2024-06-17 18:33 (UTC)
Last Updated: 2026-01-04 18:35 (UTC)

Latest Comments

yochananmarqos commented on 2026-01-04 04:21 (UTC)

@jonasmalacofilho: No, not currently. Perhaps I should have said, "...you're essentially suggesting creating specific package guidelines for GNOME Shell Extensions."

jonasmalacofilho commented on 2026-01-04 04:18 (UTC)

Are there specific packaging guidelines for GNOME Shell Extensions though? Guidelines exist for GNOME programs (which allow the use of tarballs from gnome.org), but not (that I can find) for Shell extensions.

yochananmarqos commented on 2026-01-04 03:56 (UTC)

@jonasmalacofilho: I understand your point, however this isn't the place for such a discussion as you're essentially suggesting changing package guidelines for GNOME Shell Extensions.

jonasmalacofilho commented on 2026-01-04 03:43 (UTC) (edited on 2026-01-04 03:44 (UTC) by jonasmalacofilho)

@yochananmarqos, in general, yes, building from upstream is better. However, I think this might be an exception worth considering.

First, to clarify, the extension submitted to the GNOME registry is still a source code distribution. Yes, it's built from the TS code in GitHub, but it's still on a similar level to, for example, the SQLite amalgamation or PyPI source dists.

Next, I also don't follow your point about validation. Again, to be clear, I'm talking about the fact that every version of every extension published on the GNOME registry is reviewed for malicious code and behavior (i.e. audited). And I'd argue that audits are, yes, desirable before packaging. Not always practical, but desirable.

TL:DR: one source distribution -- the GitHub tag archive -- is not audited and currently doesn't yet include a lock file (so every time we just need to hope today isn't the day one of the dev dependencies is affected by a supply chain attack), while the other -- GNOME registry -- doesn't pull external dependencies and has been reviewed by a person. This is why I made the (perhaps not so intuitive) suggestion bellow.

yochananmarqos commented on 2026-01-04 02:36 (UTC)

@jonasmalacofilho: No, packages build from source. Also, extension validation is not related to packaging.

jonasmalacofilho commented on 2026-01-02 20:10 (UTC)

Given that extensions on extensions.gnome.org are reviewed (as published there), maybe it would be better to fetch from there?

oneeyedwilly commented on 2025-09-26 05:32 (UTC)

Thanks for the fix

oneeyedwilly commented on 2025-09-25 07:55 (UTC)

Extension does not work with gnome-shell 49, an issue has already submitted upstream: https://github.com/domferr/tilingshell/issues/402.

This patch resolves: https://pastebin.com/raw/i6yYFuYE

yochananmarqos commented on 2024-09-10 19:31 (UTC)

@georgelpreput: Thanks for the heads up, it's fixed now.

georgelpreput commented on 2024-09-10 14:43 (UTC) (edited on 2024-09-10 14:55 (UTC) by georgelpreput)

Doesn't want to build on my system: https://pastebin.com/raw/ZruZraUe

Edit: Just installed it indipendently through Gnome, and it seems to work OK, just not through the AUR.