From: Jeroen Roovers <jer@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] SRC_URI in metadata.xml
Date: Fri, 10 Aug 2012 16:21:27 +0200 [thread overview]
Message-ID: <20120810162127.493a455a@marga.jer-c2.orkz.net> (raw)
In-Reply-To: <1344600203.17434.3.camel@kanae>
On Fri, 10 Aug 2012 14:03:23 +0200
Gilles Dartiguelongue <eva@gentoo.org> wrote:
> 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)
1) The information in metadata.xml is inaccurate, it's a hint. When it
fails, nothing of value is lost since the ebuild (supposedly) has
what you want.
2) SRC_URI is precise.
3) SRC_URI can change over time, and across versions (even with all the
variables in place).
4) Backward compatibility.
5) The inversion of your question: Why should we start handling SRC_URI
outside ebuilds and eclasses? Or, how would that be practical,
advantageous, an improvement on the current situation.
jer
next prev parent reply other threads:[~2012-08-10 14:22 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 ` Jeroen Roovers [this message]
2012-08-10 14:24 ` [gentoo-dev] SRC_URI " 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 ` [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=20120810162127.493a455a@marga.jer-c2.orkz.net \
--to=jer@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