Arch Linux User Repository

Search Criteria

Enter search criteria

Search by

Keywords

Out of Date

Sort by

Sort order

Per page

Package Details: rakarrack-git a620840-2

Package Actions

Git Clone URL:	https://aur.archlinux.org/rakarrack-git.git (read-only, click to copy)
Package Base:	rakarrack-git
Description:	Stereo digital effects processor with Jack support
Upstream URL:	http://rakarrack.sourceforge.net
Keywords:	audio bass effect guitar
Licenses:	GPL3
Conflicts:	rakarrack
Provides:	rakarrack
Submitter:	VirtualTam
Maintainer:	None
Last Packager:	VirtualTam
Votes:	3
Popularity:	0.000202
First Submitted:	2015-08-22 19:39 (UTC)
Last Updated:	2015-09-21 19:24 (UTC)

Dependencies (6)

alsa-utils (alsa-utils-git^AUR)
fftw (fftw-amd^AUR)
fltk (fltk-git^AUR)
jack^AUR (jack2-git^AUR, pipewire-jack-git^AUR, pipewire-full-jack-git^AUR, jack2, pipewire-jack)
libxpm (libxpm-git^AUR)
git (git-git^AUR, git-gl^AUR) (make)

Required by (0)

Sources (1)

rakarrack

Latest Comments

VirtualTam commented on 2015-09-28 21:19 (UTC)

@sekret: agreed -only providing the Git revision is not very helpful to help differentiating package versions Given the slow activity on the main repo (there are active -yet experimental- forks though), the pkgver() could be formed as follows: - <last release number>.r<number of commits in the repo>.<HEAD revision> - 0.6.1.r1733.a620840 Don't know if there is much sense keeping the "0.6.1" part in this case, as it was issued in 2010...

sekret commented on 2015-09-24 13:12 (UTC)

Your pkgver function isn't ideal, because it doesn't output the actual version of the package. Unfortunately the devs don't provide tags, so "git describe" doesn't show anything. So what you could do is this: printf "0.r%s.%s" "$(git rev-list --count HEAD)" "$(git rev-parse --short HEAD)" This is kind of "standard" for such packages. That way tools like cower can see updates, if you change something in the PKGBUILD.