On Thu, 01 Jan 2026 at 08:45:27 -0500, Jeremy Bícha wrote:
I don't understand why bootstrapping can't use
pkg.sysprof.nogui,pkg-sysprof.nounwind
instead of pkg.glib2.0.nosysprof
I wonder whether it would be worthwhile to standardize a nogui
build-profile? It seems to be a reasonably common pattern, used in
src:sysprof and src:malcontent among others.
We have to do 90% of the work for either a standard or non-standard
build-profile for "without the GTK GUI" in src:malcontent *anyway*,
because the GUI needs Flatpak, which needs libseccomp, so it isn't
immediately portable to every architecture.
My guess would be that nogui is probably more widely applicable than
nogtk/noqt/etc.; a few packages (like src:libportal) might still want a
way to disable GTK and Qt GUIs individually, but it seems fine for that
to be a package-specific/non-standard (pkg.) build profile, and
bootstrapping will probably want to use the larger hammer of turning off
GUIs completely.
A possible specification:
Name: nogui
C: N (content of binary packages can't change)
S: Y (set of binary packages can change)
Description: Disable graphical user interfaces and GUI-related libraries
smcv
