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 E4F59139694 for ; Mon, 5 Jun 2017 15:51:50 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 95AC5E0E63; Mon, 5 Jun 2017 15:51:40 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 4C03EE0E52 for ; Mon, 5 Jun 2017 15:51:40 +0000 (UTC) Received: from katipo2.lan (unknown [203.86.205.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: kentnl) by smtp.gentoo.org (Postfix) with ESMTPSA id B3154341948 for ; Mon, 5 Jun 2017 15:51:38 +0000 (UTC) Date: Tue, 6 Jun 2017 03:51:11 +1200 From: Kent Fredric To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] [RFC] Addition of a new field to metadata.xml Message-ID: <20170606035111.7f1c4c99@katipo2.lan> In-Reply-To: References: <20170602130903.334b0d03@katipo2.lan> <2816064.Ipx2b8F6kQ@note> <20170603023827.0d4531fa@katipo2.lan> <1496415085.16111.0.camel@gentoo.org> <20170603032221.35fd3fe4@katipo2.lan> <1496476708.10646.1.camel@gentoo.org> Organization: Gentoo X-Mailer: Claws Mail 3.15.0-dirty (GTK+ 2.24.31; x86_64-pc-linux-gnu) 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 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_//Dsskl6EWETeOcKCefsJNi5"; protocol="application/pgp-signature" X-Archives-Salt: fe56bd5e-f17b-4a7f-96fe-f1e755bb98dc X-Archives-Hash: 651698ae9d6aaf3b047c313880deb209 --Sig_//Dsskl6EWETeOcKCefsJNi5 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Mon, 5 Jun 2017 11:40:15 -0400 Alec Warner wrote: > Do we really need to store and distribute this data though? Aggregating this kind of data by cross-referencing multiple providers and then trying discovery against debians equivalents of that, while workable, would be likely fragile and unpredictable. If you can determine this list yourself from the existing data, I'd suggest we start with that, and then see how painful it is to do on the fly. I'd expect the round-trip times to resolve such questions would be little expensive, so you'd want a sort of job that does this periodically and creates an index outside of the repository, and then services can query *that* for things like "Can haz an screenshots?"=20 And then, it could be reasonable to then simplify this proposal such that the typical usage of introducing additional data would be to exclusively augment data that can't be discovered by other means. This would solve *both* the problems of "hard to automate" and "too much cruft in the repo", while keeping the hand-edited metadata close to the package definitions. --Sig_//Dsskl6EWETeOcKCefsJNi5 Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEPZazbI/qrFT1o9rn6FQySxNmqCAFAlk1ff0ACgkQ6FQySxNm qCDZTBAAvLKsm+la4gTD/oQKJ8PTi35ACFgHtYSSpWbZJRhmsRU0ktqJ5Rkguad0 bJnXXgmQ96znGCLllrhHY7DYp0OugAdj6SFKarOElxmW2zaohU0enrchoSvzuydU Qxq9p5qlRU5YL6CjPjnSxOoms0+9ian4tWQ20m9iPJ3ut/AjQ9HiB5ork7SubCsM keyizvJYSfvwJdBkPjypF+YDLtSRx4nUJ021+nVuLj9FDc18BNgJyB2T0LABdJ2d GUNHPXrQKObM04bLYk57oqAnMbZMxebmF4aedGR50C0sbk8BxmOiO2xR3LSrkqia ura42PoKyvq57IFDpio/s/He57c+GlahuJtBM0HE4OozaBXHZOBKnbWJmwGM/7Us yH4tVG8NE7iKarnlDcexOIUpLmHmGqAlMSiChdFqzyCjkie/99Ptv8Nvfw4uYr/5 lVoP0POqW8NpGqSkLhlJAqSQwZqnWy+l2tqgPWDSMeNtU6MRMFiVXH/6mHTz6PVl IHrTEvoI3+Y3PDtzJn7p98ZnYMhv6hSNH6oSdoz2Rbx3nWfAIGvI6vo4zuKht/zx RGgidz9SAIt9rzKnHAgMyMBfmMHrlfhiyTQg7CDL1dmpTya7+mOvR8WpLfQCMQLR a2NyaBXGJRWHyBpEy1c3mYkVILhVJ+5TNYjzUQzavCmA67L3NNM= =TSVj -----END PGP SIGNATURE----- --Sig_//Dsskl6EWETeOcKCefsJNi5--