Jun 2, 2025 03:38:54 zac <[email protected]>: > Hello, > > 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. > > 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 > pkgver=1.0 > pkgrel=1 > pkgdesc="Fast and lightweight DNS proxy as ad-blocker" > arch=("any") > url="https://github.com/0xERR0R/blocky"; > license=("0BSD") > depends=( > "openrc" > ) > optdepends=( > "blocky: blocky" > "blocky-bin: blocky" > ) > source=( > "blocky.initd" > ) > sha256sums=( > "6ad6361614b16ddac6ce9e8d5f8e9b9e8c07e95115f59311e5e38b88ccbb51e3" # > blocky.initd > ) > > package() { > install -D -v -m755 blocky.initd $pkgdir/etc/init.d/blocky > }
I believe you only need to change the version if upstream actually updates the content of the package, in other words, unless the script breaks and upstream fixes it or upstream rewrites or update the script for some other reason, you can probably leave it as is. The openrc script itself is what is meant by upstream, not what package it's meant to accompany. -- Kusoneko GPG: https://kusoneko.moe/gpg.txt https://kusoneko.moe
