summarylogtreecommitdiffstats
AgeCommit message (Collapse)Author
2017-12-11Update maintainer infoJeremy Audet
2016-05-03backport fix for ffmpeg-3.0Christoph Gysin
2016-02-20move test of libgroove.pc to check()Christoph Gysin
2016-02-18update package releaseChristoph Gysin
2016-02-18remove conflictsChristoph Gysin
libgroove-git already specifies conflicts=(libgroove). It is not necessary to specify conflicts in both directions.
2016-02-18add .gitignoreChristoph Gysin
2016-02-18separate CMake options, one per lineChristoph Gysin
2016-02-18simplify sed statementChristoph Gysin
2016-02-18fix creating build dirChristoph Gysin
mkdir will fail if the directory already exists. Also, the build dir is only needed in build().
2016-02-18Drop ccache from `options` arrayJeremy Audet
Default compilation options are listed in `/etc/makepkg.conf`. These options can be overridden on a per-package basis via the `options` array. For some reason, libgroove lists `ccache` as an option. This is problematic for several reasons: * Listing ccache as a compilation option requires that the user have ccache installed. While this certainly helps with repeated compilations, it is of no use to a user who is compiling and installing a program just once. This is presumably the common case for AUR users. * If a user does not have ccache installed and it is listed as a compilation option, makepkg will refuse to run and ask for ccache to be installed. This can be confusing. The comment posted by gcurse to the libgroove aurweb page [1] on 2016-02-15 is an example of this. Drop `ccache` from the list of compilation options. [1] https://aur.archlinux.org/packages/libgroove/
2015-07-06Update to version 4.3.0Jeremy Audet
2015-07-06Initial commit (version 4.2.1)Jeremy Audet