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)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id A101415800A for ; Mon, 17 Jul 2023 18:14:46 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 2FE2EE0898; Mon, 17 Jul 2023 18:14:43 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (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 pigeon.gentoo.org (Postfix) with ESMTPS id E3971E0883 for ; Mon, 17 Jul 2023 18:14:42 +0000 (UTC) Date: Mon, 17 Jul 2023 14:14:39 -0400 From: Ionen Wolkens To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Package stabilization groups Message-ID: Mail-Followup-To: gentoo-dev@lists.gentoo.org References: <87lefebgdr.fsf@gentoo.org> <8c7d2e05-3bbf-5e12-de38-7dc96ba0cf54@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="wnc3+wLl+EJgAqeb" Content-Disposition: inline In-Reply-To: <8c7d2e05-3bbf-5e12-de38-7dc96ba0cf54@gentoo.org> X-Archives-Salt: faf12d85-94cd-4653-b677-9ad52b7e3c06 X-Archives-Hash: 11f4bb45f498d4e18ee8a40ba4dd5dcf --wnc3+wLl+EJgAqeb Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jul 17, 2023 at 08:34:45PM +0300, Arthur Zamarin wrote: > Hmm, I was thinking the opposite (maintaining it in parallel place to > the package would be harder), but if you say so (and you help maintain > huge clusters of packages so I believe you) then I think we don't have > any good reason to go with per package metadata.xml entry? imo seeing/setting it all in one place is simpler, ultimately it's about managing a group (whole) and I don't think is super important on the individual packages. e.g. [qt] dev-qt/package dev-qt/package2 Can visualize and don't have to go set this in each one of them. fwiw repo-cd could be given a hook to grep that file, and be able to say that a package is part of a stabilization group -- and if nattka automatically looks at groups it'll also be hard to overlook when filing bugs. Regardless of approach, some kind of central file (generated or not) would certainly be nice not to end up grepping all metadata.xml in the tree to figure out which packages are part of a group. --=20 ionen --wnc3+wLl+EJgAqeb Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCAAdFiEEx3SLh1HBoPy/yLVYskQGsLCsQzQFAmS1hQ8ACgkQskQGsLCs QzQ2dAgAyiUlzEeMznyE2ZZOk3k8Jfu98dThIHWBBPS3P8bxUsHAQx7GMRuS4iaN sVuECivNv9XHZhUm9NeRJUGZzjHRwA8L3dNXSBP+jIrnsezJzyZJ0pSKxmGKOrve bJyyrdfeuXUUh8x6tP2ZduEhixP7dFDTzGEHR+CcD4iXbVnBglFSBK9Cx2UdR4sA i/cCHJbWMiJenZ8ugRE7CZbzJG+EYfFeae0mRuElj9fA5HxAhPu1eRmBVLwYVdCZ 6VfLLPF8HsOyH1DIIWtK5hQMVNc4aesEOleJZCV73PnZpqvCR4ThGpcCOK98YIZa 2jJmDMYwU07g2FyXbNqQZ8PlNhTnLg== =/ZhA -----END PGP SIGNATURE----- --wnc3+wLl+EJgAqeb--