As described in this bug https://github.com/atlas-engineer/nyxt/issues/2743 nyxt no longer builds with webkit-gtk:5 - the current solution is to hard block :5, but as the comment describes, all that's needed is more fine-tuneable use flags. Reproducible: Always
There are multiple slots to accommodate this, USE unfortunately wouldn't allow e.g. a package needing the gtk3 version and another needing the gtk4 version to coexist. :4 is SOUP2=on + GTK4=off :4.1 is SOUP2=off + GTK4=off :5 is SOUP2=off + GTK4=on
If nyxt build system picks webkit-gtk-5.0 package while not working with it, then that's a nyxt build system issue to be fixed. In particular, this is completely wrong: https://github.com/atlas-engineer/nyxt/blob/master/libraries/web-extensions/Makefile#L4-L5
Combined with cl-webkit bindings, potentially some cl-gtk thing and so on, things look even more nuanced to get everything to actually use the same compatible packages. This is purely something for the lisp stack to figure out, we can't just go and hard block a SLOT that other packages need and providing a SOUP2+GTK4 wouldn't help any (and also is not and will not be a thing from webkit-gtk upstream) and I don't see that as even the actual symptom here. Your original request isn't something we can provide, it's precisely what we provide via the SLOTs already, as upstream also provides parallel-installable libraries for each of the allowed combinations and that's where our SLOTs come from. A package mustn't just pick "any available API" when it isn't even compatible with all of them (which is not really a thing as you can't easily just make a package be compatible with both gtk3 and gtk4 at the same time anyways).
Understood, fair enough!
