From: Nikos Chantziaras <realnc@arcor.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Trying SRC_URI first during fetching
Date: Wed, 10 Jun 2009 02:36:04 +0300 [thread overview]
Message-ID: <h0mrl1$bpl$1@ger.gmane.org> (raw)
In-Reply-To: <9D738A58-9395-405F-9B4A-0FF7FFA686D0@stellar.eclipse.co.uk>
Stroller wrote:
>
> On 9 Jun 2009, at 05:16, Nikos Chantziaras wrote:
>
>> Normally, portage will try fetching from GENTOO_MIRRORS during an
>> emerge and SRC_URI comes last. I want to reverse this; try SRC_URI
>> first and if that fails, only then proceed to fetch from
>> GENTOO_MIRRORS. Doable?
>
> This is undesirable behaviour - te mirrors exist because SRC_URI may
> often have limited bandwidth.
Understandable, but my problem lies in "ebuild digest" of my own ebuilds
and ebuilds of third-party overlays. Along the URLs tried by portage is
one that seems to need over a minute to reply with "401 not found".
This is highly annoying. I would want to try SRC_URI in those cases first.
Of course that doesn't mean SRC_URI should be tried by default first. I
never suggested that and look what happened to this thread :P
next prev parent reply other threads:[~2009-06-09 23:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 4:16 [gentoo-user] Trying SRC_URI first during fetching Nikos Chantziaras
2009-06-09 7:41 ` Neil Bothwick
2009-06-09 13:04 ` Stroller
2009-06-09 13:28 ` Neil Bothwick
2009-06-09 13:34 ` Alan McKinnon
2009-06-09 13:48 ` Volker Armin Hemmann
2009-06-09 14:01 ` Alan McKinnon
2009-06-09 23:36 ` Nikos Chantziaras [this message]
2009-06-10 7:11 ` [gentoo-user] " Neil Bothwick
2009-06-10 7:19 ` Nikos Chantziaras
2009-06-10 7:25 ` Neil Bothwick
2009-06-09 15:56 ` [gentoo-user] " Arttu V.
2009-06-09 16:08 ` Alan McKinnon
2009-06-09 18:26 ` Volker Armin Hemmann
2009-06-09 18:49 ` Alan McKinnon
2009-06-09 21:57 ` Neil Bothwick
2009-06-09 22:10 ` Alan McKinnon
2009-06-09 22:17 ` Volker Armin Hemmann
2009-06-09 22:35 ` Alan McKinnon
2009-06-09 22:53 ` Volker Armin Hemmann
2009-06-09 23:27 ` Neil Bothwick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='h0mrl1$bpl$1@ger.gmane.org' \
--to=realnc@arcor.de \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox