From: Scott Taylor <security@303underground.com>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] Feature request
Date: Thu, 01 Jan 2004 13:14:36 -0700 [thread overview]
Message-ID: <1072988075.16658.18.camel@Star.BerthoudWireless.net> (raw)
In-Reply-To: <200401012054.53508.pauldv@gentoo.org>
Whatever came of comment #14 of bug 28806 - That is something along the
lines of what i'd like to see. In my own network, I have a central
server with its /usr/portage/distfiles available locally by anonymous
ftp. This way, my local mirror has any file used on itself (or
prefetched for my other workstations by way of an emerge --fetchonly).
So, I do have files on this machine that should be checked first,
regardless of whether a build is marked "nomirror". For any network that
has local repositories either ftp/nfs/samba/whatever could find that
useful too. Lists of other groups of mirrors (sourceforge, etc) are also
good things to allow customization on. Its just my luck to want some
huge source that it tries to get from a slow sourceforge mirror on the
other side of the world...
On Thu, 2004-01-01 at 12:54, Paul de Vrieze wrote:
> On Wednesday 31 December 2003 15:34, Allen Parker wrote:
> > I think it'd be a good idea for portage-ng to include better localization
> > features (specifically relating to mirrors). I've recently been plagued
> > with RESTRICT="nomirror" being set in recent mysql 4.0.x ebuilds causing my
> > filefetching operations to take considerable amounts of time when they
> > should actually be the fastest. (my example is 30kb/s from argentina
> > instead of the regular 4Mb/s from gentoo.mirrors.pair.com)
>
> To me this has more to do with the mirror selection algorithm than with
> localization. Mirrors from the mirror:// pseudo-protocol should be chosen in
> such a way that they are both load-balanced, and optimized for local users.
> Preferably this should work without user interference.
>
> The same should hold for multiple source locations in the ebuild itself, but
> it is less important.
>
> Paul
--
Scott Taylor - <security@303underground.com>
work, n.:
The blessed respite from screaming kids and
soap operas for which you actually get paid.
--
gentoo-portage-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-01-01 20:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1AbhRM-0007Ja-C9@smtp.gentoo.org>
2004-01-01 19:54 ` [gentoo-portage-dev] Feature request Paul de Vrieze
2004-01-01 20:14 ` Scott Taylor [this message]
2004-01-01 20:24 ` Paul de Vrieze
2004-01-01 20:43 ` Scott Taylor
2004-01-01 21:19 ` Paul de Vrieze
2004-01-01 21:43 ` Scott Taylor
2004-01-02 5:08 ` Brian
[not found] <E1AbhRH-0004kq-Lq@smtp.gentoo.org>
2004-01-02 20:20 ` Marius Mauch
2003-12-31 14:34 Allen Parker
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=1072988075.16658.18.camel@Star.BerthoudWireless.net \
--to=security@303underground.com \
--cc=gentoo-portage-dev@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