dist: PKGBUILDs & AUR packages #23

kbity · 2026-05-19T18:46:21+02:00

kbity commented

2026-05-19 18:46:21 +02:00

title; see:
https://aur.archlinux.org/packages/wbij
https://aur.archlinux.org/packages/wbij-bin

title; see: https://aur.archlinux.org/packages/wbij https://aur.archlinux.org/packages/wbij-bin

kbity added 2 commits

2026-05-19 18:46:27 +02:00

[dist] add PKGBUILDs for wbij and wbij-bin fa3855196a

[readme] add aur package note f55a4c0516

maleszka reviewed

2026-05-20 11:27:24 +02:00

maleszka left a comment

Thank you very much!

I wonder, do we want to provide anything other than wbij-bin? I think wbij-bin will be the one that we would be recommending to people.

I know that AUR community usually prefers compiling stuff from source but... I wonder if it would cause only unnecessary confusion. Also zig versions are changing very fast and current pkgbuild is already broken on current mainstream zig.

What do you think?

Thank you very much! I wonder, do we want to provide anything other than `wbij-bin`? I think `wbij-bin` will be the one that we would be recommending to people. I know that AUR community usually prefers compiling stuff from source but... I wonder if it would cause only unnecessary confusion. Also zig versions are changing very fast and current pkgbuild is already broken on current mainstream `zig`. What do you think?

README.md Outdated

I suggest just adding the following line to the current readme:

There is also an AUR package wbij-bin maintained by @kbity : )

What do you think?

I suggest just adding the following line to the current readme: > There is also an AUR package [wbij-bin](https://aur.archlinux.org/packages/wbij-bin) maintained by @kbity : ) What do you think?

screen.png

28 KiB

Seems okay for the time being; will adopt this

dist/PKGBUILD Outdated

					
				@ -0,0 +7,4 @@

				url="https://repos.adamm.rocks/maleszka/wbij"

				license=('GPL-2.0-or-later')

				depends=('fzf')

				makedepends=('zig>=0.15.2' 'zig<0.16.0')

I don't know what are "best practices" in the AUR world but is it better to have zig0.15 here?

I don't know what are "best practices" in the AUR world but is it better to have `zig0.15` here?

dist/PKGBUILD Outdated

					
				@ -0,0 +14,4 @@

				build() {

				  cd "${srcdir}/${pkgname}"

				  zig build -Doptimize=ReleaseFast

we should ship ReleaseSafe builds

we should ship `ReleaseSafe` builds

👍 1

kbity commented

2026-05-20 19:02:10 +02:00

I know that AUR community usually prefers compiling stuff from source but... I wonder if it would cause only unnecessary confusion. Also zig versions are changing very fast and current pkgbuild is already broken on current mainstream zig.

Fair point; the source package should have a specific version of Zig pinned; referencing one of your comments- yeah I should've marked zig0.15 as a dependency rather than zig<0.16.

I wonder, do we want to provide anything other than wbij-bin? I think wbij-bin will be the one that we would be recommending to people.

That's also a valid point, honestly I might drop the source package for the time being and reinstate it when 1.0 is released. Also, nothing wrong with recommending the binary package by default imho.

> I know that AUR community usually prefers compiling stuff from source but... I wonder if it would cause only unnecessary confusion. Also zig versions are changing very fast and current pkgbuild is already broken on current mainstream `zig`. Fair point; the source package should have a specific version of Zig pinned; referencing one of your comments- yeah I should've marked `zig0.15` as a dependency rather than `zig<0.16`. > I wonder, do we want to provide anything other than `wbij-bin`? I think `wbij-bin` will be the one that we would be recommending to people. That's also a valid point, honestly I might drop the source package for the time being and reinstate it when 1.0 is released. Also, nothing wrong with recommending the binary package by default imho.

👍 1

kbity commented

2026-05-20 19:08:02 +02:00

Actually, I think we can keep the source package up and just direct everyone to wbij-bin by default; it's no extra burden for me to keep it up to date.

Actually, I think we can keep the source package up and just direct everyone to `wbij-bin` by default; it's no extra burden for me to keep it up to date.

👍 1

kbity force-pushed feat/pkgbuilds from f55a4c0516 to caa604000f

2026-05-20 19:12:36 +02:00

Compare

maleszka approved these changes

2026-05-20 19:16:17 +02:00

maleszka left a comment

Everything's perfect! Thank you : )

This pull request can be merged automatically.

This branch is out-of-date with the base branch

You are not authorized to merge this pull request.

View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u origin feat/pkgbuilds:feat/pkgbuilds

git switch feat/pkgbuilds

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main

git merge --no-ff feat/pkgbuilds

git switch feat/pkgbuilds

git rebase main

git switch main

git merge --ff-only feat/pkgbuilds

git switch feat/pkgbuilds

git rebase main

git switch main

git merge --no-ff feat/pkgbuilds

git switch main

git merge --squash feat/pkgbuilds