Hi Alec, Thank you very much for your explanation.
I'll keep it in my notes. Best, Samuel On 3/31/20 11:41 PM, Alec Warner wrote: > In general I'd avoid using the mirror system as URI simplification too > much; a lot of the idea is to avoid hardcoding specific hosts. E.g. > for the gentoo mirrors we want to avoid hardcoding a *specific* mirror > in the SRC_URI, so mirror://gentoo lets us say "any gentoo mirror will > do." Often other thirdpartymirror systems act similarly. You see this > commonly where mirrors are divided by region. > > example.com/mirror <http://example.com/mirror> # "global / us" > example.au/mirror <http://example.au/mirror> # "australia" > example.co.uk/mirror <http://example.co.uk/mirror> # "UK" > > From a layout perspective these are the same, but you would not want > to hardcode "https://example.com/mirror" in the ebuild, because then > australian users are routed to the US..which is wasteful. So we use a > generic: > > "mirror://example" > > And we potentially pick the best mirror at fetch time. > > This is mostly spelled out > in: https://devmanual.gentoo.org/ebuild-writing/variables/#third-party-mirrors > > If you have a bunch of packages that share a common domain and its not > sharded (there is only 1 host serving it) then you should consider > using an eclass to share data between your ebuilds and not use > thirdpartymirrors just to share a hostname. > > -A
signature.asc
Description: OpenPGP digital signature
