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.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 3888B138334 for ; Sun, 29 Dec 2019 02:19:26 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 23A24E0A97; Sun, 29 Dec 2019 02:19:22 +0000 (UTC) Received: from smtp.gentoo.org (mail.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id C6066E0A88 for ; Sun, 29 Dec 2019 02:19:21 +0000 (UTC) Received: from localhost (pool-108-44-175-72.clppva.fios.verizon.net [108.44.175.72]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: bman) by smtp.gentoo.org (Postfix) with ESMTPSA id 6F22134DC9C for ; Sun, 29 Dec 2019 02:19:20 +0000 (UTC) Date: Sat, 28 Dec 2019 21:19:18 -0500 From: Aaron Bauman To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Keywordreqs and slacking arch teams Message-ID: <20191229021918.GB6770@bubba.lan> References: <20191228222702.017cbbaa@katipo2.lan> <20191228093509.GB2033@gentoo.org> <20191229000543.001631d9@katipo2.lan> <20191229003225.71f34cdd@katipo2.lan> <20191229004254.5c8a3f5f@katipo2.lan> 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="b5gNqxB1S1yM7hjW" Content-Disposition: inline In-Reply-To: X-Archives-Salt: 78a9d52f-d76a-4b2e-a97e-a43b2b828aba X-Archives-Hash: ed6ed2bcaa15e5a9d91bc8b75e3837ec --b5gNqxB1S1yM7hjW Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Dec 28, 2019 at 10:05:02AM -0800, Alec Warner wrote: > On Sat, Dec 28, 2019 at 3:43 AM Kent Fredric wrote: >=20 > > On Sat, 28 Dec 2019 11:35:49 +0000 > > Michael 'veremitz' Everitt wrote: > > > > > Note: we're nnot acttually talking about replacing portage here, just > > > creating a tool ((((thiink php script web tthingy)) that will do some= of > > > the pre-screeninng worrrrk that AT hate (eg.... what kensiington did > > with > > > stable-bbot) > > > > > > * with apologies for keyboard/remote-access lagggg creating typo hell. > > > > But, doing that requires viewing realised copies of ebuilds, which > > requires interpreting eclasses and variable interpolation, which > > requires bash sourcing, which requires a mountain of portage hell. > > >=20 > > Yes, sharing the stable-bot logic would probably be fine. > > > > But it doesn't use a database AFAIK, it would likely just be making use > > of the MD5Cache (either directly, or indirectly via portage APIs) > > > > But I won't be volunteering, because I won't touch python. > > >=20 > You could of course work together with someone else to write the tool? >=20 > -A Ah, you found the Achilles heel. It is much easier to postulate on the mail= ing list, use big words, and then say you just won't do that thing because tools/languages such. Perl though... --=20 Cheers, Aaron --b5gNqxB1S1yM7hjW Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCAAdFiEEDA48qNrrn8VVVcst4yp5f7HQy3AFAl4IDSYACgkQ4yp5f7HQ y3BiBgf+IHeygeeDkqtN15klfiJFU6YFZ3daretXlmdvGeYb1134NyaFqGOOuTh5 LqPmt451uHpRjCfThV+cvbWkEN76lxI6Nr7s33+NpRq+4DxJeCbl/GWEP7XF8gqL d0X6U3tYID3sspyhoYNB90cbo39jy1nGNNzNoTrw6GEDoy1Kk7JeQLkDHRsH6x2E Li6J/P2vosw6STLXFXBsy73FuWt6uePCxLMJZcw5dvUNIfaJ7l7W5Yc4RSnZIg24 DKG9+ZaoKcwYP5cNM/bFLn8D5S2MGHbIWQrPlh9fAPuglcPZhQLcLDOG+xHbzeg9 yCIpeB2ulNKLRipz5Bu5wQPNqxHEpQ== =/jgV -----END PGP SIGNATURE----- --b5gNqxB1S1yM7hjW--