Package Details: suil-git 0.10.24.r494.58f6da4-1

Git Clone URL: https://aur.archlinux.org/suil-git.git (read-only, click to copy)
Package Base: suil-git
Description: Lightweight C library for loading and wrapping LV2 plugin UIs (git version)
Upstream URL: http://drobilla.net/software/suil/
Licenses: ISC
Conflicts: suil, suil-svn
Provides: libsuil-0.so, suil, suil-docs
Submitter: SpotlightKid
Maintainer: SpotlightKid
Last Packager: SpotlightKid
Votes: 1
Popularity: 0.82
First Submitted: 2016-02-03 16:48 (UTC)
Last Updated: 2025-12-06 15:12 (UTC)

Required by (25)

Sources (1)

Latest Comments

ilovemikael commented on 2025-12-07 23:06 (UTC)

Thank you for linking that document: I was looking for it to no avail (briefly saw it when first trying to build, but later couldn't recall the source) when initially commenting on your packages, as it lends credence to my argument that there should be no UI toolkit dependencies. It was precisely upon seeing this document that my frustration with this package began, as it does the exact opposite of what upstream advises.

The purpose of Suil is to abstract plugin UI toolkits away from host code. To achieve this, Suil dynamically loads modules for the toolkits in use. The main Suil library does NOT depend on any toolkit libraries, and its package shouldn't either (otherwise, for example, every LV2 host in the distribution would depend directly on Gtk and Qt). Individual modules (like libsuil_x11_in_gtk3.so) should be packaged separately and themselves depend on the involved libraries or toolkits. These packages should also be versioned as described above to support parallel installation. Please do not make the main Suil package strongly depend on any toolkit package, this defeats the purpose of Suil and will cause problems for users who need to avoid a particular toolkit dependency for whatever reason. "Weak" or "recommended" dependencies are fine, the important thing is that users are able to avoid particular toolkits if they choose.

As you can see, suil's purpose is literally to not do what this script does; I hate fighting, but this seems so obvious to me that I am utterly befuddled by your decision.

SpotlightKid commented on 2025-12-06 15:13 (UTC)

@ilovemikael: optdepends can indeed be makedepends as well. The latter are needed (and checked by meson during build) at build-time, but are not required at run-time. suil loads the UI kit libraries dynamically at runtime.

See: https://gitlab.com/lv2/suil/-/blob/main/PACKAGING.md

ilovemikael commented on 2025-12-01 21:46 (UTC) (edited on 2025-12-01 21:49 (UTC) by ilovemikael)

Hi, this package should have the line rm "$pkgdir"/usr/share/doc/$pkgname/{single,}html/.buildinfo removed as the .buildinfo files it tries to delete don't exist.

Additionally, I built this package without qt5-base and gtk2 and it obviously compiled without a hitch (they are listed in optdepends, so for it to be optional, it cant be a makedep!); I use gtk3 and thus didn't try building without it, but I would assume it can be removed too since it's listed in optdeps with the former two.