I am in the process of adding few new packages to my AUR. Among the targets, there are DISTRHO plugins built on top of DPF. I am planning to package the whole bundle (see this thread) but also the different plugins independently, in case users want to select only few (or build also the JACK standalone version of the plugins).
So, it should go as follows: package DPF first and then require it as a dependency for all the various DPF based plugins. However, I am not too sure how to correctly install DPF on an Arch system. Apparently, most of the included files are headers and I feel like I don't have to build anything. Which is why all I came up with is to just copy all the files to /usr/include/dpf:
Code: Select all
# Maintainer: CrocoDuck <crocoduck dot oducks at gmail dot com>
pkgname=dpf-git
pkgver=r531.9b69b9d
pkgrel=1
pkgdesc="DISTRHO Plugin Framework"
arch=('i686' 'x86_64')
url="http://distrho.sourceforge.net/"
license=('custom:ISC')
depends=('make' 'python')
makedepends=('git')
provides=("${pkgname%-*}")
conflicts=("${pkgname%-*}")
source=("${pkgname%-*}::git://github.com/DISTRHO/DPF")
md5sums=('SKIP')
pkgver() {
cd "${pkgname%-*}"
printf "r%s.%s" "$(git rev-list --count HEAD)" "$(git rev-parse --short HEAD)"
}
package() {
# Install headers:
cd "${pkgname%-*}"
mkdir -p "$pkgdir/usr/include/${pkgname%-*}/"
cp -r "dgl" "$pkgdir/usr/include/${pkgname%-*}/dgl"
cp -r "distrho" "$pkgdir/usr/include/${pkgname%-*}/distrho"
cp -r "utils" "$pkgdir/usr/include/${pkgname%-*}/utils"
# This is just to generate the online docs, right?
#cp "dpf.doxygen" "$pkgdir/usr/include/${pkgname%-*}/dpf.doxygen"
# What about this? MVerb builds without it. Is it a kdevelop thing?
#cp "dpf.kdev4" "$pkgdir/usr/include/${pkgname%-*}/dpf.kdev4"
# Install documentation:
mkdir -p "$pkgdir/usr/share/doc/${pkgname%-*}"
cp -r "lac" "$pkgdir/usr/share/doc/${pkgname%-*}/lac"
cp "README.md" "$pkgdir/usr/share/doc/${pkgname%-*}/README.md"
# Install license:
install -Dm 644 "LICENSE" "$pkgdir/usr/share/licenses/$pkgname/LICENSE"
}
However, I am not too sure the above is right as I never produced a headers package before (is this actually a headers package?