Package Details: oomox 1.4.3_1.2.9_20171005-1

Git Clone URL: https://aur.archlinux.org/oomox.git (read-only)
Package Base: oomox
Description: Graphical application for generating different color variations of Numix/Materia theme (GTK2, GTK3), gnome-colors and ArchDroid icon themes. Have a hack for HiDPI in gtk2.
Upstream URL: https://github.com/actionless/oomox
Licenses: GPL3
Conflicts: oomox-git
Provides: oomox
Submitter: TCGman
Maintainer: TCGman
Last Packager: TCGman
Votes: 21
Popularity: 1.025286
First Submitted: 2016-07-16 14:58
Last Updated: 2017-12-03 10:26

Latest Comments

ondoho commented on 2017-10-18 16:34

I'm still having problems with flat-plat.
i have to SKIP its md5sum, but i also have to replace "Flat-Plat" with "materia-theme" in the source url, and once in prepare.
now it at least installs, but i haven't tested yet if oomox actually works this way.

TCGman commented on 2017-08-28 21:01

@actionless it should be fixed now (at least it seems to work on my system)

actionless commented on 2017-08-28 20:15

version of `flat-plat` is too old (it's a blocker)

hogar1977 commented on 2017-07-19 13:06

@TCGman

Validity check for 1.2.7.tar.gz is failing during latest update...

TCGman commented on 2017-05-04 16:33

@annoyingduck exactly ! Although oomox-git's version number gets updated whenever a new version is released, so there are no big problems regarding updates for this one. This package is just for the consistency of building the package at the exact version it's showing

annoyingduck commented on 2017-05-04 16:13

@TCGman always learning on Arch! Thanks, this all makes sense to me now. Basically GIT based AUR packages can change day to day even with the same version number - Pamac may not show an update. So rebuilding a GIT package will "update" it, while the standard packages are more or less stable and will show and update on version changes. If I understood that correctly.

TCGman commented on 2017-05-03 21:00

@annoyingduck Yes, the versions are the same, but the git package clones oomox from git and will always be at the latest master commit. Building the git package twice will not always produce the same package if new commits were added between each build. This package uses the latest tag instead, which means it will stay the same no matter when you install it. This package is like a stable version, whereas the git package is a bleeding edge version.

annoyingduck commented on 2017-05-03 20:44

@TCGman Any particular reason to choose your package vs the git package? Versions are the same.