On Monday 06 March 2006 13:18, 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.... > > 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.
You seem to be missing my point, let's pick an ebuild at random, say app-admin/cronolog whose SRC_URI="http://cronolog.org/download/${P}.tar.gz", no the automirror script will need to know to mirror at in /c/ on the distfiles mirrors, that's outside of portage, however when I emerge cronolog portage will need to know that the location, on the distfiles mirrors, of cronolog, is now the equivilent of mirror://gentoo/${firstchar}, taking distfiles.gentoo.org as an example that would mean http://distfiles.gentoo.org/distfiles/c/${P}.tar.gz, that means a portage modification in my book. > > 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. And I was saying I agree since the same work has to be done to handle all the automirrored stuff anyway. -- Daniel Ostrow Gentoo Foundation Board of Trustees Gentoo/{PPC,PPC64,DevRel} [EMAIL PROTECTED]
pgpCvttJt2IaE.pgp
Description: PGP signature