From: Corentin Chary <iksaif@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] SRC_URI in metadata.xml
Date: Sat, 11 Aug 2012 13:55:49 +0200 [thread overview]
Message-ID: <CAHR064gS4owXDgN=MuWnTL9Wo8y0iZhAS0jKvpx7N3ZaADX8xA@mail.gmail.com> (raw)
In-Reply-To: <50256B3D.3040101@flameeyes.eu>
On Fri, Aug 10, 2012 at 10:12 PM, Diego Elio Pettenò
<flameeyes@flameeyes.eu> wrote:
> On 10/08/2012 13:05, Corentin Chary wrote:
>> Right, our proposal is not here to replace SRC_URI, it's here to fix
>> the cases where SRC_URI can't be sanely used to guess new upstream
>> versions (strange mangling rules, unbrowsable directories, etc...).
>
> Yes I guess Jeroen was just saying why we shouldn't abandon it as Gilles
> proposed.
>
> FWIW for the rest it feels right to me. Although this starts to add up
> to the reasons why at least metadata.xml should be validated by schema,
> and not DTD.
Maybe .. We plan to use <watch xmlns="http://euscan.iksaif.net"> to
avoid editing metadata.dtd (for now).
What do you think about format propositions ? Current format looks
like what was given in the examples, but mgorny feels that something
more xmlish would be better.
--
Corentin Chary
http://xf.iksaif.net
next prev parent reply other threads:[~2012-08-11 11:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-10 11:11 [gentoo-dev] [RFC] euscan: Need to add more upstream info in metadata.xml Federico "fox" Scrinzi
2012-08-10 12:03 ` Gilles Dartiguelongue
2012-08-10 14:21 ` [gentoo-dev] SRC_URI " Jeroen Roovers
2012-08-10 14:24 ` Diego Elio Pettenò
2012-08-10 20:05 ` Corentin Chary
2012-08-10 20:12 ` Diego Elio Pettenò
2012-08-11 11:55 ` Corentin Chary [this message]
2012-08-11 22:43 ` Alec Warner
2012-08-11 23:53 ` Diego Elio Pettenò
2012-08-13 10:25 ` Dirkjan Ochtman
2012-08-13 14:50 ` Diego Elio Pettenò
2012-08-13 10:51 ` Gilles Dartiguelongue
2012-08-10 20:04 ` [gentoo-dev] [RFC] euscan: Need to add more upstream info " Corentin Chary
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHR064gS4owXDgN=MuWnTL9Wo8y0iZhAS0jKvpx7N3ZaADX8xA@mail.gmail.com' \
--to=iksaif@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox