On Wed, 10 Jun 2009 02:36:04 +0300, Nikos Chantziaras wrote:
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
On 06/10/2009 10:11 AM, Neil Bothwick wrote:
On Wed, 10 Jun 2009 02:36:04 +0300, Nikos Chantziaras wrote:
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
On Wed, 10 Jun 2009 10:19:11 +0300, Nikos Chantziaras wrote:
With your own ebuilds there's no point in them trying to contact the
mirrors, so put RESTRICT=nomirror in the ebuild.
Thanks. That's pretty much what I was looking for.
That's what I thought, which is why I posted it when you
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
4 matches
Mail list logo