1 |
On Thu, 10 Apr 2003 11:41:39 +0200 |
2 |
Spider <spider@g.o> wrote: |
3 |
|
4 |
> > if you want the latest binary for mutt |
5 |
> > running on 486 you need file |
6 |
> > mutt-1.5.4.486.tar.gz |
7 |
> > |
8 |
> > for pentium |
9 |
> > mutt-1.5.4.586.tar.gz |
10 |
> |
11 |
> why not ia32/486/mutt-1.5.4.tbz2 |
12 |
> why not ia32/586/mutt-1.5.4.tbz2 |
13 |
|
14 |
Because portage downloads files in one dir ... the ebuild can be in that format .. |
15 |
there are many options .. but having as much details in the file name would make it easer to find files locally on on the net ... |
16 |
|
17 |
but it's just an idea :) |
18 |
|
19 |
> > this is logical .. and workable. |
20 |
> |
21 |
> and my idea gives less files to list ;) |
22 |
|
23 |
but harder to implement in portage .. I can see portgae admins frothing at themouth already about this thread ;P hehehe |
24 |
|
25 |
> Stick to the defaults, if people want to change them, they can rebuild. |
26 |
> Reduces our headache, and the problems with dependencies. |
27 |
|
28 |
I agree with that one :) |
29 |
|
30 |
> unfortunately, Bittorrent works best on larger files, due to design, and |
31 |
> it has to be in "constant use" to be worthy. |
32 |
|
33 |
I'm not very familiar with it .. so was just a mention :) |
34 |
|
35 |
> Gnutella is a viable system, if we change the way the clients work and |
36 |
> hook up. Background daemon to stay connected and share, wide node-splay |
37 |
> and then attempting to reconfigure so each node will "try" to connect to |
38 |
> nodes that have what we want. follow that up with a front-end client to |
39 |
> send download requests from the dameon and theres something that might |
40 |
> work. |
41 |
|
42 |
This can release alot of load from the distfile mirrors ... and should really be looked at, |
43 |
esp if one of the mirrors go down etc etc there is another machine with the files availible .. |
44 |
|
45 |
> No, dont suggest giFT/OpenFT. It doesnt scale anymore:/ Freenet is an |
46 |
> idea, as is gnunetd, but both are laggy protocols, which is rather |
47 |
> negative in our case since people mind speed. |
48 |
|
49 |
I'm not very clued up on p2p .. I don't personally use it often if at all, but I think |
50 |
distributed system for distfiles can be very successful for gentoo ... for both source and binary systems. |
51 |
|
52 |
> And yes, package signing would be really important for such a case. |
53 |
|
54 |
agreed :) |
55 |
|
56 |
Henti |
57 |
|
58 |
-- |
59 |
gentoo-dev@g.o mailing list |