From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 7DB861580EB for ; Mon, 26 May 2025 09:52:03 +0000 (UTC) Received: from lists.gentoo.org (bobolink.gentoo.org [140.211.166.189]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) (Authenticated sender: relay-lists.gentoo.org@gentoo.org) by smtp.gentoo.org (Postfix) with ESMTPSA id 6951834317F for ; Mon, 26 May 2025 09:52:03 +0000 (UTC) Received: from bobolink.gentoo.org (localhost [127.0.0.1]) by bobolink.gentoo.org (Postfix) with ESMTP id 5C58C1104AE; Mon, 26 May 2025 09:51:16 +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 bobolink.gentoo.org (Postfix) with ESMTPS id 96C49110287 for ; Mon, 26 May 2025 09:51:15 +0000 (UTC) Received: from eversor (unknown [166.62.140.157]) (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) (Authenticated sender: ionen) by smtp.gentoo.org (Postfix) with ESMTPSA id 2ECEB3430A4 for ; Mon, 26 May 2025 09:51:15 +0000 (UTC) Date: Mon, 26 May 2025 05:51:12 -0400 From: Ionen Wolkens To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] RFC: new global USE=websockets Message-ID: Mail-Followup-To: gentoo-dev@lists.gentoo.org References: 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="iIVEfEt3EQFsMdam" Content-Disposition: inline In-Reply-To: X-Archives-Salt: c98b61d6-ec01-43ff-8efd-51affa2700ee X-Archives-Hash: fccee8c9552b063759e4ccee5121f6a9 --iIVEfEt3EQFsMdam Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, May 26, 2025 at 05:45:49AM -0400, Ionen Wolkens wrote: > On Mon, May 26, 2025 at 07:18:48AM +0200, Micha=C5=82 G=C3=B3rny wrote: > > On Sun, 2025-05-25 at 13:49 -0700, Robin H. Johnson wrote: > > > On Sun, May 25, 2025 at 05:07:09PM +0200, Micha=C5=82 G=C3=B3rny wrot= e: > > > > I'd like to propose a new global use flag: > > > >=20 > > > > websockets: Enable support for WebSocket protocol > > > request: please use the singular USE=3Dwebsocket, rather than plural. > >=20 > > Convince all the people who named it USE=3Dwebsockets. >=20 > May possibly have originated from Qt which always named its module > Qt WebSockets. or python, forgot it uses dev-python/websockets too.. well if we have two packages named that, I guess it fits anyway. >=20 > Personally don't mind either way other than renaming sockets to socket > would be more disruptive than the other way around given the consumers, > dependencies, and not having a USEmove. > --=20 > ionen --=20 ionen --iIVEfEt3EQFsMdam Content-Type: application/pgp-signature; name=signature.asc -----BEGIN PGP SIGNATURE----- iQEzBAABCAAdFiEEx3SLh1HBoPy/yLVYskQGsLCsQzQFAmg0OZAACgkQskQGsLCs QzR65ggAghs0aplKSRW05y4S+DtNeSKjaffJz/SdHSjbh9jjMDfLnrisnxV2MC2R Nj08lCpV//XecYNaqn/lHEbIJnY/wQXVMLaUWZxS2SF8942nCFFEO+l6rRnbmXSy KaptTeTrYA7FXDI43qzjUeM+xzk9Nhpb39smWE3GEmvRDYqU+eK8zkMERfGTSNjW kuIo/RI2x0/M4q2ROnjiADyuCaJYWxVar2WLMLrAa/RgBiREIRA6R5O6/+6c6WgD AyJRu0USB/Z3cCoy805zBJ6Pt1EX3xixydXbP0b1K44ZkVeDkrIpcwLVwZi+F2SU /9qBKGSn8ldDWcgAqHSkYIn9cLkOfA== =I2Ay -----END PGP SIGNATURE----- --iIVEfEt3EQFsMdam--