You are not logged in.
Hey all,
I've got a small Go tool called op-forward that forwards 1Password CLI calls across SSH boundaries, so op works inside headless VMs and containers while the biometric prompt happens on the host. Just cut 1.0.0 and I already publish deb/rpm/apk repos for it. I'd like to get it on the AUR as op-forward-bin whenever accounts open up again (saw the aur-general thread from yesterday, not trying to relitigate that, happy to wait or be an early test case if the sponsored registration model lands).
The wiki says this is one of the places to get a PKGBUILD looked at before it ever hits the AUR, so here it is. It's generated by a script in the repo and CI builds and installs it in an Arch container on every release. Would appreciate a sanity check:
# Maintainer: op-forward maintainers <ekovshilovsky@users.noreply.github.com>
pkgname=op-forward-bin
pkgver=1.0.0
pkgrel=1
pkgdesc="Forward 1Password CLI across SSH boundaries with biometric auth"
arch=('x86_64' 'aarch64')
url="https://github.com/ekovshilovsky/op-forward"
license=('MIT')
provides=('op-forward')
conflicts=('op-forward')
source=("LICENSE-${pkgver}::https://raw.githubusercontent.com/ekovshilovsky/op-forward/v${pkgver}/LICENSE")
source_x86_64=("${pkgname}-${pkgver}-x86_64.tar.gz::https://github.com/ekovshilovsky/op-forward/releases/download/v1.0.0/op-forward_${pkgver}_linux_amd64.tar.gz")
source_aarch64=("${pkgname}-${pkgver}-aarch64.tar.gz::https://github.com/ekovshilovsky/op-forward/releases/download/v1.0.0/op-forward_${pkgver}_linux_arm64.tar.gz")
sha256sums=('8a0fa447b28249b817329f83c08c1bb3f3307598b3b41a0b0d64aa8ee3f516f8')
sha256sums_x86_64=('710e8fbdaaeba7469a94b982a5c839aea6d1ac1c6a83eab1b7e63c1d9ba001af')
sha256sums_aarch64=('ba211e17cb20d065fa263a7732d0533fe8b96e0da2b48e8acc1d746a2791af23')
package() {
install -Dm755 "${srcdir}/op-forward" "${pkgdir}/usr/bin/op-forward"
install -Dm644 "${srcdir}/LICENSE-${pkgver}" "${pkgdir}/usr/share/licenses/${pkgname}/LICENSE"
}Repo: https://github.com/ekovshilovsky/op-forward
Thanks!
Eugene
Offline
Packages that build from source tend to be a lot more popular (and easier to check) then packages using pre-built binaries .
Are the build resources needed high in cpu time, memory use, power, download size and such ?
If yes, that could be a valid reason to provide a -bin package .
In case you want to try creating a package for building from source, read https://manual.archlinux.page/package-guidelines/go/ and https://manual.archlinux.page/package-guidelines/
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline