On Sat, Oct 26, 2024 at 1:03 AM Robin H. Johnson <robb...@gentoo.org> wrote: > > On Tue, Oct 22, 2024 at 11:24:29PM -0400, Eli Schwartz wrote: > > Apache has a mirror network, which only covers the most recent release > > of any given package. They also have an additional site which does not > > appear to be a CDN, and is throttled and can maybe ban you if you use it > > too much. Unfortunately, it is also the ONLY way to actually get > > historic releases of many packages. > > > > Use it, and use it last -- after every other mirror has been tried, > > which should handle latest releases. In combination with GENTOO_MIRRORS > > this should ensure that users can actually download software when > > needed, without running afoul of throttling. > This does not actually do it "last" as you claim. > > Portage shuffles the list of thirdpartymirrors: > https://gitweb.gentoo.org/proj/portage.git/tree/lib/portage/package/ebuild/fetch.py#n1140 > > While it increases mirror burden; this should likely be done as a > distinct thirdpartymirror: > apache-historical https://archive.apache.org/dist/ > > And that gets used in ebuilds when distfiles fall off the main mirrors > [until such time as strictly ordered behavior is available].
I assume Eli was trying to avoid having to update old ebuilds. I don't really see any point in adding an apache-historical entry in thirdpartymirrors; just inline https://archive.apache.org/dist/ into SRC_URI if the ebuild requires it.
