From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 2810015806E for ; Mon, 22 May 2023 09:36:31 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 67774E0A8D; Mon, 22 May 2023 09:36:27 +0000 (UTC) Received: from smtp.gentoo.org (woodpecker.gentoo.org [140.211.166.183]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 1D15AE0A7F for ; Mon, 22 May 2023 09:36:27 +0000 (UTC) Date: Mon, 22 May 2023 05:36:23 -0400 From: Ionen Wolkens To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] [PATCH] profiles/targets/desktop: enable USE=vulkan by default Message-ID: Mail-Followup-To: gentoo-dev@lists.gentoo.org References: <20230521214850.1659618-1-sam@gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="vnkz7ociYDF3IsEk" Content-Disposition: inline In-Reply-To: X-Archives-Salt: 11b1969e-ceb8-44f3-b0e3-89b9c65dcdf4 X-Archives-Hash: 48c9590ea07f31548950f8157468cce7 --vnkz7ociYDF3IsEk Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, May 22, 2023 at 10:13:59AM +0200, Ulrich Mueller wrote: > >>>>> On Sun, 21 May 2023, Sam James wrote: >=20 > > 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. >=20 > That's a non-sequitur. No reason to not have it on doesn't imply that > there is a reason to have it on. >=20 > 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. =20 >=20 > > In particular, Steam expects it for plenty of games to work, >=20 > 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). --=20 ionen --vnkz7ociYDF3IsEk Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCAAdFiEEx3SLh1HBoPy/yLVYskQGsLCsQzQFAmRrN5cACgkQskQGsLCs QzQ96wf+Mr79g4ITvhtXX5TGcH4NqgyisN50F24/DGupTUtmeOLvjRirhbHPT4w6 lEzxK9R3dCyIxYsfJbI+nHymiIV7Dy7dvcxMVU/xoerWX2BPsScdag3XnDFVQGoK ZVMIvs7FUAnvhtMhFNoPVESGKgTkOka1k3b3d/t1wrkzjeQuxxCh2BeMRl5m+3+s FTpmtREzuyA7HCl2n4XYNNhk8TtNdtYELvX8XfU28NuaMmi3rtdz/36qKrG0RC4B SiLmPCCPvI69FGOc+KUwzFgY/ukED0kuNrsyoApmudNR1DtiuB/YrqVOjoeInEy8 1Qc1y+aOUUB6RyLXXpz8kDUfr/82vQ== =Uv4W -----END PGP SIGNATURE----- --vnkz7ociYDF3IsEk--