On Mon, May 22, 2023 at 10:13:59AM +0200, Ulrich Mueller wrote:
> >>>>> On Sun, 21 May 2023, Sam James wrote:
> 
> > Ionen pointed this out again today and it made me look back at it;
> > there's no reason to not have vulkan on by default for desktop
> > profiles.
> 
> That's a non-sequitur. No reason to not have it on doesn't imply that
> there is a reason to have it on.
> 
> Also, shouldn't we avoid enabling local flags in profiles?

I keep forgetting that this is still not global either, guess it'll
ideally need another step first.
 
> 
> > In particular, Steam expects it for plenty of games to work,
> 
> That's what USE dependencies are for.

For often-used USE, that doesn't mean that every users should have to
enable it manually when they try to emerge the package. It would
notably be annoying if, e.g. opengl wasn't default either (if opengl
can be a default, I don't see why vulkan can't be in 2023).

I see this as a sane desktop default much like having png, jpeg, etc..
enabled.

Steam, games, and similar applications also come from several sources
not necessarily managed by portage all while expecting typical GPU
features (and png/jpeg support!) to work without having to dig in
USE flags on a desktop profile more than necessary. It's a better
out-of-the-box user experience.

Vulkan dependencies are also fairly trivial, typically it's just about
pulling vulkan-loader, headers, and glslang plus having support on mesa
or nvidia-drivers (always enabled regardless for the latter).
-- 
ionen