You are not logged in.
Hi
I'm trying to create a PKGBUILD for the gTile extension for gnome-shell, which currently can't be updated in the repos, since there is no github-release for version 52, which supports Gnome 44. However it's available on extensions.gnome.org.
I like to do without the package, which is available in the AUR, as this does not fall back on the stable version but compiles the master branch directly.
Now I tried to create my own PKGBUILD, which downloads the zip file from extensions.gnome.org.
Here it is:
pkgname=gnome-shell-extension-gtile
pkgver=52
pkgrel=1
pkgdesc="A window tiling extension for Gnome"
arch=('any')
url="https://extensions.gnome.org/extension/28/gtile/"
license=('GPL2+')
depends=('gnome-shell')
makedepends=('unzip')
conflicts=("${pkgname}-git")
source=("${pkgname}-${pkgver}.zip::https://extensions.gnome.org/extension-data/gTilevibou.v52.shell-extension.zip")
sha256sums=("a624292ae3b6c7ba0f27e3569236f8051d32b2e7c6e4503848b9181cbfb7ecd6")
package() {
install -d "${pkgdir}/usr/share/gnome-shell/extensions/gTile@vibou"
unzip -o ${pkgname}-${pkgver}.zip -d ${pkgdir}/usr/share/gnome-shell/extensions/gTile\@vibou
install -d "${pkgdir}/usr/share/glib-2.0/schemas"
ln -s /usr/share/gnome-shell/extensions/gTile@vibou/schemas/org.gnome.shell.extensions.gtile.gschema.xml \
"${pkgdir}/usr/share/glib-2.0/schemas"
}
The problem is, whenever I install the package and logout and then back into gnome, the extension is not visible nor can't it be activated.
Is there a problem, how Gnome 44 handles extensions?
I even took the original PKGBUILD as a reference:
https://github.com/archlinux/svntogit-c … k/PKGBUILD
When installing the official package, the extension is visible in the gnome-extensions application, but not usable, since it's only supported for Gnome 43.
I really can't tell, where the problem is.
The files are all available in their paths, so nothing is missing.
Thank you very much for helping.
Last edited by Veldora (2023-05-12 11:24:04)
Offline
No idea (I don't use gnome) , but if you check https://github.com/gTile/gTile/commits/master you'll notice that the last commit to master IS the commit that makes it version 52 .
A simple way to build from source and ensure you always get version 52 is to build that exact commit .
git clone the files for gnome-shell-extension-gtile-git and open its PKGBUILD in your fav text editor.
Look for the source= line ( source=("${pkgname%-git}::git+https://github.com/gTile/gTile.git") )
Add the commit hash for that specific commit jus before the closing " so the line becomes
source=("${pkgname%-git}::git+https://github.com/gTile/gTile.gitf19decf6b4296d89158303c5cb5e49d953d2896f")
build with makepkg , install with pacman -U .
Last edited by Lone_Wolf (2023-05-12 10:08:56)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Very interesting procedure.
Didn't know, that you could put the commit-hash behind .git, to clone the exact commit.
But is it normal, that if I clone it, that git asks for my GitHub credentials, even though the project is public?
Offline
No it's not. Seems I forgot to add the #commit= part that makes this work to the source= line .
source=("${pkgname%-git}::git+https://github.com/gTile/gTile.git#commit=f19decf6b4296d89158303c5cb5e49d953d2896f")
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Brilliant!
This is a suitable solution without great effort.
Thank you very much.
Offline