On 2018-03-27 22:00, David Haller wrote:
> So, using your example, portage looks up the mirror for mirror://gnu
> by looking in /etc/portage/mirrors (if it exists) and
> /usr/portage/profiles/thirdpartymirrors for a line with the word "gnu"
> at the beginning, and then tries the mirrors specified there. I.e.:
Thanks, this helps. I have a related follow-up question.
Sometimes, the SRC_URI in fact consists of multiple URIs. What is
confusing about that is that in some cases the individual URI clearly
refer to copies of the same file (I'm guessing this provides redundant
locations where to download it from), while in other cases they're
clearly different files (for example upstream patches to be downloaded
separately). There are even ebuilds when _both_ cases happen at the
same time, such as media-libs/freetype-2.9 :
SRC_URI="mirror://sourceforge/freetype/${P/_/}.tar.bz2
mirror://nongnu/freetype/${P/_/}.tar.bz2
utils? ( mirror://sourceforge/freetype/ft2demos-${PV}.tar.bz2
mirror://nongnu/freetype/ft2demos-${PV}.tar.bz2 )
doc? ( mirror://sourceforge/freetype/${PN}-doc-${PV}.tar.bz2
mirror://nongnu/freetype/${PN}-doc-${PV}.tar.bz2 )"
So, WTH is the semantics of this? How does portage know which URIs are
for the main tarball and which are the extras? It has to know that to
avoid downloading the main tarball twice.
--
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
To reply privately _only_ on Usenet and on broken lists
which rewrite From, fetch the TXT record for no-use.mooo.com.
