Package Details: luv-icon-theme-git 1:r836.f236f33-1

Git Clone URL: https://aur.archlinux.org/luv-icon-theme-git.git (read-only, click to copy)
Package Base: luv-icon-theme-git
Description: The spiritual successor to Flattr, a flat but complex icon theme for freedesktop environments.
Upstream URL: https://github.com/Nitrux/luv-icon-theme
Keywords: colorful flat flattr-icon-theme-git icon modern theme
Licenses: custom:CC BY-SA 4.0
Conflicts: flattr-icon-theme, luv-icon-theme
Provides: flattr-icon-theme, luv-icon-theme
Submitter: edh
Maintainer: edh
Last Packager: edh
Votes: 87
Popularity: 0.32
First Submitted: 2016-04-21 20:14 (UTC)
Last Updated: 2020-06-04 08:09 (UTC)

Latest Comments

1 2 3 Next › Last »

edh commented on 2020-06-04 08:11 (UTC)

@andykluger Sorry about that. I seemingly stilled relied an old version of the repository. This should be fixed now.

andykluger commented on 2020-06-04 06:17 (UTC)

@edh well now my local version is 1:continuous.master.r5.gf236f33-1 while the AUR version is 1:r834.38c20d3-1, which looks "newer" as well.

edh commented on 2020-06-02 19:02 (UTC)

@andykluger Thanks for the comment! Unfortunately, upstream pruned all tags from the repository and completely got rid of any fixed version counter. I increased the epoch accordingly.

andykluger commented on 2020-06-01 17:29 (UTC)

Currently pkgver produces results like continuous.master.r3.g38c20d3, which is sorted as "older" than the AUR version 0.4.9.12.r2.gc2b0d15, so that the package always looks out of date on a user's system.

orestisf commented on 2018-07-29 22:30 (UTC)

The correct link seems to be https://github.com/Nitrux/luv-icon-theme (s/NitruxSA/Nitrux/)

edh commented on 2017-05-10 13:37 (UTC)

@arcanis Thanks for letting me know. I updated the package accordingly.

arcanis commented on 2017-05-10 10:58 (UTC)

repo structure has been changed; dark theme seems to be removed, root directory has been renamed to "Luv"

edh commented on 2016-10-11 14:19 (UTC)

@rushaur Introducing a $_pkgname is not required. The build should work fine either way. You problem is most likely unrelated. Try removing /tmp/makepkg and build from a fresh copy. By the way you can stick as many forward-slashes in there and it would not change a thing. The filesystem is capable of ignoring them. Just try it yourself.

rushaur commented on 2016-10-11 12:22 (UTC) (edited on 2016-10-11 12:37 (UTC) by rushaur)

With the 'original' PKGBUILD I get this error: ==> ERROR: /tmp/makepkg//luv-icon-theme-git is not a clone of https://github.com/NitruxSA/luv-icon-theme.git (Notice the two slashes). Here is the PKGBUILD that worked for me with few tweaks (german locale installed,didn't test without): # Maintainer: Gordian Edenhofer <gordian.edenhofer@gmail.com> # Submitter: Steffen L. Norgren (incongruous) <steffen[at]norgren[dot]ca> pkgname=luv-icon-theme-git _pkgname=luv-icon-theme pkgver=r678.961ba1f pkgrel=1 pkgdesc="The spiritual successor to Flattr, a flat but complex icon theme for freedesktop environments." arch=('any') url="https://github.com/NitruxSA/luv-icon-theme" license=('custom:CC BY-SA 4.0') depends=('librsvg') makedepends=('git') provides=("flattr-icon-theme=${pkgver}" "luv-icon-theme=${pkgver}") conflicts=('flattr-icon-theme' 'luv-icon-theme') source=('git+https://github.com/NitruxSA/luv-icon-theme.git') md5sums=('SKIP') pkgver() { cd "${srcdir}/$_pkgname" ( set -o pipefail git describe --long 2>/dev/null | sed 's/\([^-]*-g\)/r\1/;s/-/./g' || printf "r%s.%s" "$(git rev-list --count HEAD)" "$(git rev-parse --short HEAD)" ) } package() { cd "${srcdir}/$_pkgname" install -dm755 "${pkgdir}/usr/share/icons/Lüv" install -dm755 "${pkgdir}/usr/share/icons/Lüv Dark" cp -dpr --no-preserve=ownership ./Lüv/* "${pkgdir}/usr/share/icons/Lüv" cp -dpr --no-preserve=ownership ./Lüv\ Dark/* "${pkgdir}/usr/share/icons/Lüv Dark" install -Dm644 "./Lüv/LICENSE" "${pkgdir}/usr/share/licenses/${pkgname}/LICENSE" install -Dm644 "./CREDITS" "${pkgdir}/usr/share/licenses/${pkgname}/CREDITS" rm "${pkgdir}"/usr/share/icons/{Lüv,Lüv\ Dark}/LICENSE }

edh commented on 2016-06-25 18:29 (UTC)

@jguer Unfortunately upstream chose to include special characters everywhere in the project. Since makepkg is still able to create a proper package, I chose to stick as close to the source as possible without changing naming schemas.