Simon Stelling wrote:
Daniel Ostrow wrote:
Hrm, /me thinks you are missing something there, almost the entire
tree doesn't explicitly state the mirror://gentoo SRC_URI, portage
handles that automatically. That being the case portage would have
change so that the automatic lookup was mirror://gentoo/${firstchar}/.
So that is at least one portage change I can think of being required....
1925 ebuilds ( with a hacked up SRC_URI checking script )[1]
URI_check.py "mirror://gentoo"
Huh? What does it state then? AFAIK ebuilds should ALWAYS use the
mirror:// URI when possible, and since this change is only affecting our
own mirrors, it is always possible.
Sure I can still see your point about needing to manually change the
packages that do explicitly state mirror://gentoo in their SRC_URI,
but given that you would have to do the above anyway....
Huh?? My point was that we shouldn't have to change all those ebuilds
but instead just changing the mirror://gentoo-mapping.
See if we do it the ebuild way we can filter via EAPI. The ebuild has a
EAPI=2 SRC_URI, but portage is only EAPI=0, then the ebuild is
automagically filtered; as opposed to the ebuild failing miserably.
It's getting close to the point where we can finally leverage EAPI to
push features out faster because backwards compatability is maintained (
for portage ). Infra is still screwed essentially doing 2
implementations until such time as the old one can die.
I'd prefer the mirrors not be special cased in a mapping since. URI's
are URI's are URI's...
-Alec Warner
-----------------------------------------
[1] dev.gentoo.org/~antarus/URI_check.py
--
gentoo-dev@gentoo.org mailing list
