Package Details: qogir-gtk-theme 2023.05.24-1

Git Clone URL: (read-only, click to copy)
Package Base: qogir-gtk-theme
Description: Qogir is a flat Design theme for GTK
Upstream URL:
Keywords: gtk-theme qogir
Licenses: GPL3
Submitter: Bitts311
Maintainer: FirstAirBender
Last Packager: FirstAirBender
Votes: 12
Popularity: 0.008299
First Submitted: 2020-06-10 10:48 (UTC)
Last Updated: 2023-05-25 23:37 (UTC)

Dependencies (8)

Required by (0)

Sources (2)

Pinned Comments

Dwa30v commented on 2021-11-20 19:26 (UTC) (edited on 2021-11-20 19:26 (UTC) by Dwa30v)


I'm using pacman, and upgrade with sudo pacman -Syyu. I did as you suggested, removed the cache entry. I used pamac to remove and install. Then, all worked well.

Thanks for the help!

$ pamac remove qogir-gtk-theme
$ pamac install qogir-gtk-theme

Latest Comments

1 2 3 4 Next › Last »

yochananmarqos commented on 2023-03-12 23:00 (UTC) (edited on 2023-03-12 23:02 (UTC) by yochananmarqos)

@killermoehre: As long as the proper dependencies are installed (which this PKGBUILD ensures), pacman will never be called. If upstream isn't going to change it, then it could be patched out.

FirstAirBender commented on 2023-03-12 22:59 (UTC)

@killermoehre absolutely we can talk about that. I was also perusing the script after the last update and I feel it can really be improved with some modularization. Someone had opened an issue that suggested using a makefile to improve packaging for other distros, but the author basically said they have no experience with makefiles.

I honestly don't see makefile as a viable solution, but that script needs some drastic changes.

killermoehre commented on 2023-03-12 20:25 (UTC)


can we talk about how the itself is calling various package manager to install self-build packages?

Can this package be split up in the different versions, or at least manipulated in such a way that no package manager is called during package()?

FirstAirBender commented on 2023-03-08 16:06 (UTC)

@yochananmarqos done. Thanks for the reference, I didn't know that was a common pattern with theme packages

yochananmarqos commented on 2023-03-07 16:51 (UTC)

@FirstAirBender: The Arch community theme packages do not declare gtk3 at all. See the pop-gtk-theme PKGBUILD for an example

FirstAirBender commented on 2023-03-07 02:10 (UTC)

@yochananmarqos upon further thought, maybe not having gtk3 as a dependency isn't such a bad idea. It doesn't look right, but the installer for this theme doesn't seem to care what version of gtk you have as it installs themes for every one of them (including gtk4), so maybe we shouldn't be as strict either.

Let me know what you think, thanks.

FirstAirBender commented on 2023-03-07 01:51 (UTC)

@yochananmarqos I don't like that solution, but in the interest of avoiding duplicating the same package just because of dependencies, I will revert the changes, and just make the gtk2 dependencies optional.

It's unfortunate that current aur helpers do not have the capability to just build and package a single package of split packages.

yochananmarqos commented on 2023-03-07 01:10 (UTC)

@FirstAirBender: Just don't declare gtk3 as a dependency at all.

FirstAirBender commented on 2023-03-07 01:04 (UTC)

@yochananmarqos, The reason I created a separate package just for gtk2 is so that it didn't force gtk2 users to also install gtk3. Making the gtk2 dependencies optional is a fine idea, but it wouldn't make sense to also make gtk3 optional.

Do you have a better solution to this?

yochananmarqos commented on 2023-03-07 01:00 (UTC)


The Gtk 2 dependencies should be optional for the theme as was already requested here. Every other theme package does this. Creating a duplicate package makes no sense.