From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1RwsZA-0000fX-8k for garchives@archives.gentoo.org; Mon, 13 Feb 2012 09:51:24 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 19EBEE0A4A; Mon, 13 Feb 2012 09:51:15 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id B05B9E09EA for ; Mon, 13 Feb 2012 09:50:45 +0000 (UTC) Received: from mail-we0-f181.google.com (mail-we0-f181.google.com [74.125.82.181]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: djc) by smtp.gentoo.org (Postfix) with ESMTPSA id E53251B4014 for ; Mon, 13 Feb 2012 09:50:44 +0000 (UTC) Received: by werp13 with SMTP id p13so3882847wer.40 for ; Mon, 13 Feb 2012 01:50:42 -0800 (PST) Received: by 10.180.92.73 with SMTP id ck9mr23288559wib.2.1329126642221; Mon, 13 Feb 2012 01:50:42 -0800 (PST) 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 Received: by 10.216.3.1 with HTTP; Mon, 13 Feb 2012 01:50:22 -0800 (PST) In-Reply-To: References: From: Dirkjan Ochtman Date: Mon, 13 Feb 2012 10:50:22 +0100 Message-ID: Subject: Re: [gentoo-dev] RFC: upstream/watch in metadata.xml To: gentoo-dev@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 X-Archives-Salt: b513fc94-b603-46fa-a273-ef3120a33b94 X-Archives-Hash: e56a9f8ce0fd954d5d7d98ab95173cd9 On Mon, Feb 13, 2012 at 10:33, Corentin Chary wrote: > One other thing, metadata.xml already contain a remote-id tag, which > would be very great to help euscan do its job, but a lot of package > are lacking it: > - Should we patch repoman to scan SRC_URI and issue a warning when it > looks like an URI that match a well known remote-id > - Should we write a script to update metadata.xml ? It would be easy > for rubygem, pypi and pear packages. > > Any comment ? Objections ? Ideas ? I like the idea for keeping the data somewhere for known-insane cases, and metadata.xml sounds like it might be fine. But I don't think we should add anything for the likes of PyPI, if we can easily derive that we should look on PyPI some other way (i.e. for python, many packages list a PyPI page in their HOMEPAGE). Cheers, Dirkjan