| 1 |
begin quote |
| 2 |
On Thu, 10 Apr 2003 11:07:24 +0200 |
| 3 |
Henti Smith <bain@×××××××.za> wrote: |
| 4 |
|
| 5 |
|
| 6 |
> if you want the latest binary for mutt |
| 7 |
> running on 486 you need file |
| 8 |
> mutt-1.5.4.486.tar.gz |
| 9 |
> |
| 10 |
> for pentium |
| 11 |
> mutt-1.5.4.586.tar.gz |
| 12 |
|
| 13 |
why not ia32/486/mutt-1.5.4.tbz2 |
| 14 |
why not ia32/586/mutt-1.5.4.tbz2 |
| 15 |
|
| 16 |
> |
| 17 |
> etc etc .. |
| 18 |
> |
| 19 |
> this is logical .. and workable. |
| 20 |
|
| 21 |
and my idea gives less files to list ;) |
| 22 |
|
| 23 |
|
| 24 |
> USE flags. |
| 25 |
> |
| 26 |
> This is a lot more tricky as use flags will effect alot of |
| 27 |
> applications. |
| 28 |
|
| 29 |
Stick to the defaults, if people want to change them, they can rebuild. |
| 30 |
Reduces our headache, and the problems with dependencies. |
| 31 |
|
| 32 |
|
| 33 |
|
| 34 |
> |
| 35 |
> as to hosting the binaries ... maybe looking at something like |
| 36 |
> bittorrent or other p2p system would be worthwhile looking into (this |
| 37 |
> could even be investigated for the current rsync/distfiles system) but |
| 38 |
> then hash/md5/etc checking would become very importand. |
| 39 |
|
| 40 |
unfortunately, Bittorrent works best on larger files, due to design, and |
| 41 |
it has to be in "constant use" to be worthy. |
| 42 |
|
| 43 |
Gnutella is a viable system, if we change the way the clients work and |
| 44 |
hook up. Background daemon to stay connected and share, wide node-splay |
| 45 |
and then attempting to reconfigure so each node will "try" to connect to |
| 46 |
nodes that have what we want. follow that up with a front-end client to |
| 47 |
send download requests from the dameon and theres something that might |
| 48 |
work. |
| 49 |
|
| 50 |
No, dont suggest giFT/OpenFT. It doesnt scale anymore:/ Freenet is an |
| 51 |
idea, as is gnunetd, but both are laggy protocols, which is rather |
| 52 |
negative in our case since people mind speed. |
| 53 |
|
| 54 |
And yes, package signing would be really important for such a case. |
| 55 |
|
| 56 |
//Spider |
| 57 |
|
| 58 |
-- |
| 59 |
begin .signature |
| 60 |
This is a .signature virus! Please copy me into your .signature! |
| 61 |
See Microsoft KB Article Q265230 for more information. |
| 62 |
end |
Archives