From: Corentin Chary <iksaif@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] euscan: Need to add more upstream info in metadata.xml
Date: Fri, 10 Aug 2012 22:04:06 +0200 [thread overview]
Message-ID: <CAHR064je1mfyQLO_7YDEALUw7A+S4jnnL0-cY8TzAsR7dX1J-A@mail.gmail.com> (raw)
In-Reply-To: <1344600203.17434.3.camel@kanae>
On Fri, Aug 10, 2012 at 2:03 PM, Gilles Dartiguelongue <eva@gentoo.org> wrote:
> Having done some debian packaging for work, I find watch files from
> debian really helpful. Changing the format to a XML compatible one does
> not seem like a hard work so I'll probably leave that up for others to
> discuss.
>
> Since you are proposing this, a side question is:
> Why should we write SRC_URI in ebuilds if that info is now available in
> metadata.xml ? (granted that we might still want to keep over-riding
> this information in ebuilds)
It's not (only) SRC_URI, sometime it's completly different, sometimes
<watch> would contain only versionmangle since SRC_URI contains
enought informations for euscan... SRC_URI serves a totally different
purpose :).
--
Corentin Chary
http://xf.iksaif.net
prev parent reply other threads:[~2012-08-10 20:05 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
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 ` Corentin Chary [this message]
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=CAHR064je1mfyQLO_7YDEALUw7A+S4jnnL0-cY8TzAsR7dX1J-A@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