1 |
My thoughts exactly. Also IIRC portage will go through the list of |
2 |
sf.net mirrors in the same pre-determined order every time. Perhaps to |
3 |
do some quasi-load-balancing we can have it randomly go through the |
4 |
mirrors and/or allow the user to specify their preferred mirror in an |
5 |
/etc/make.conf var like: |
6 |
|
7 |
SOURCEFORGE_MIRROR=twtelecom |
8 |
|
9 |
Perhaps this won't work but I thought I'd throw it out. |
10 |
|
11 |
Don. |
12 |
|
13 |
On Tue, Jul 22, 2003 at 03:24:09PM +0200, Rainer Groesslinger wrote: |
14 |
> Perhaps you already thought about this but IMHO part of that policy should be |
15 |
> that files which are stored on a network with a good mirroring infrastructure |
16 |
> (sourceforge, kernel.org etc.) are never placed on our distfiles because it |
17 |
> is very unlikely all 10 mirrors (or how many sourceforge ever has) are down |
18 |
> and since the gentoo distfile mirrors are used before the |
19 |
> mirror://sourceforge in the ebuild it causes more traffic to the mirrors |
20 |
> (plus the space it takes) because nobody really gets it from sourceforge... |
21 |
> |
22 |
> I think we could save a lot of bandwidth _and_ space if such files aren't |
23 |
> placed on the gentoo mirrors if not absolutly neccessary, I don't see a real |
24 |
> reason why we need to put hundreds of files on the gentoo mirrors which are |
25 |
> already stored on a very good mirroring system. |
26 |
|
27 |
-- |
28 |
gentoo-dev@g.o mailing list |