Hi zac,
> I'm hoping to submit an AUR package which is just an OpenRC script for
> another package. The main package is `blocky` and I'll be calling my
> package `blocky-openrc` as such.
>
> I'm not sure if I should version my package separately, or if it should
> match the version of Blocky. I'm hesitant to version it by Blocky
> because it would be annoying to have to update the package version every
> time a new version of Blocky is released, even though nothing in the
> OpenRC script has changed.
I’d personally go for separate versioning. There is not much benefit to
matching the versioning if the openrc script doesn’t need to be changed
on most updates.
That also seems to be the case for other -openrc packages [1].
A few notes on the overall PKGBUILD:
> Here is the PKGBUILD. I figured I'd post it in case there's other
> feedback anyone might have.
>
> # Maintainer: zacoons <zac [at] zacoons [dot] com>
>
> pkgname=blocky-bin-openrc
The name should be blocky-openrc because this package is not packaging
binaries.
> pkgver=1.0
> pkgrel=1
> pkgdesc="Fast and lightweight DNS proxy as ad-blocker"
You should probably clarify that this is only the openrc script.
> arch=("any")
> url="https://github.com/0xERR0R/blocky";
> license=("0BSD")
> depends=(
> "openrc"
> )
> optdepends=(
> "blocky: blocky"
> "blocky-bin: blocky"
> )
Since blocky-bin provides blocky, you can just depend on blocky. Users
will get asked which one to install if they don’t have one already.
> source=(
> "blocky.initd"
> )
> sha256sums=(
> "6ad6361614b16ddac6ce9e8d5f8e9b9e8c07e95115f59311e5e38b88ccbb51e3" #
> blocky.initd
> )
>
> package() {
> install -D -v -m755 blocky.initd $pkgdir/etc/init.d/blocky
> }
You should quote the last part because $pkgdir could contain spaces.
--
tippfehlr
[1]
https://aur.archlinux.org/packages?O=0&SeB=nd&K=-openrc&outdated=&SB=p&SO=d&PP=50&submit=Go
