Arch Linux

jschillem

Member

Registered: 2025-05-06

Posts: 1

Reviewing PKGBUILD for Bitwig Connect Control Panel

With the release of the Bitwig Connect audio interface, there is not an existing AUR package for it's accompanying control panel software. This is my first ever attempt at making a AUR package, so I'm seeking feedback on the PKGBUILD before submitting it to the AUR.

I created the PKGBUILD using the existing bitwig-studio PKGBUILD as a guide, as it's created by the same developer. There were 3 main points where I am concerned and could use some guidance:

1. I am unsure how to tell what dependencies are necessary for my package, The only dependency I know for certain is necessary is xcb-imdkit. In my own testing of installing the package, I was unable to launch the program without it, finding the missing library in my crash log.

2. I am not sure the process for generating the sha256sums field, and am unsure if it is necessary.

3. Within the data.tar.zst archive, I was unable to find any LICENSE file for this software like there was for bitwig-studio. If none is provided, what is best course of action for filling out the license field?

Thank you in advance for any review/feedback!

# Maintainer: Justin Schilleman <justin@schilleman.com>
# Upstream: Bitwig GmbH <support@bitwig.com>

pkgname='bitwig-connect-control-panel'
pkgver='1.0'
_pkgver='1.0'
pkgrel='1'
pkgdesc='Control Panel software for the Bitwig Connect audio interface'
arch=('x86_64')
url='https://www.bitwig.com/'
license=('custom')
depends=('xdg-utils' 'xcb-util-wm' 'xcb-imdkit' 'libbsd')
source=("bitwig-connect-control-panel-${pkgver}.deb::https://www.bitwig.com/dl/?id=600&os=installer_linux")
sha256sums=('SKIP')
options=(!strip)

package() {
  bsdtar -xf ${srcdir}/data.tar.zst -C ${pkgdir}/
}

Scimmia

Fellow

Registered: 2012-09-01

Posts: 12,666

Re: Reviewing PKGBUILD for Bitwig Connect Control Panel

1. namcap is one method, it'll tell you of obvious missing or unneeded deps. It won't catch everything and will have false positives, but it's better than nothing.
2. It is necessary. sha256sum is a command line utility, or let makepkg do it for you with -g
3. Nothing on the site anywhere? Or in the software itself?

Now, basic review.
_pkgver is useless
You need to quote any paths with variables you don't control, like $srcdir and $pkgdir.
This is proprietary software? If it's not something that could be built from source, your pkgname is fine. If it could be built from source, you'd need a -bin suffix.

Last edited by Scimmia (2025-05-07 03:29:20)