public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alin Nastac <mrness@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Policy on RESTRICT=[no]mirror and use of mirror://foo/
Date: Fri, 06 May 2005 07:37:07 +0300	[thread overview]
Message-ID: <427AF473.8020709@gentoo.org> (raw)
In-Reply-To: <200505051430.18082.cshields@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 754 bytes --]

Corey Shields wrote:

>At one point in time someone suggested that we may as well utilize other 
>people's mirror networks that are already out there, rather than our own.  
>This then got implemented for stuff like sourceforge packages.
>
>Unfortunately this plays hell for lots of people.  If you have a local mirror, 
>then you get files fast and without using your outside bandwidth.  Having to 
>wait for a file from some mirror in zimbabwe because "that package already 
>has a mirror structure" defeats the purpose of running a local mirror.
>  
>
I know only one mirror network who could worth the hassle: cpan.
Perl has a nice geographically distributed network of mirrors. Too bad
portage can't automatically select the closest cpan mirror. :(

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]

  reply	other threads:[~2005-05-06  4:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-05 21:04 [gentoo-dev] Policy on RESTRICT=[no]mirror and use of mirror://foo/ Robin H. Johnson
2005-05-05 21:20 ` Ciaran McCreesh
2005-05-05 21:30 ` Corey Shields
2005-05-06  4:37   ` Alin Nastac [this message]
2005-05-06  5:53     ` Robin H. Johnson
2005-05-06  6:06       ` Brian Harring
2005-05-06 21:08   ` Chris Gianelloni
2005-05-07 16:42     ` Lance Albertson
2005-05-05 22:01 ` Mike Frysinger
2005-05-05 22:06   ` Lance Albertson
2005-05-05 22:21     ` Corey Shields
2005-05-05 22:22       ` Lance Albertson

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=427AF473.8020709@gentoo.org \
    --to=mrness@gentoo.org \
    --cc=gentoo-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