From: Spider <spider@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Binary release of gentoo
Date: Thu, 10 Apr 2003 11:41:39 +0200 [thread overview]
Message-ID: <20030410114139.4ad76a8b.spider@gentoo.org> (raw)
In-Reply-To: <20030410110724.520bdf43.bain@tcsn.co.za>
[-- Attachment #1: Type: text/plain, Size: 1796 bytes --]
begin quote
On Thu, 10 Apr 2003 11:07:24 +0200
Henti Smith <bain@tcsn.co.za> wrote:
> if you want the latest binary for mutt
> running on 486 you need file
> mutt-1.5.4.486.tar.gz
>
> for pentium
> mutt-1.5.4.586.tar.gz
why not ia32/486/mutt-1.5.4.tbz2
why not ia32/586/mutt-1.5.4.tbz2
>
> etc etc ..
>
> this is logical .. and workable.
and my idea gives less files to list ;)
> USE flags.
>
> This is a lot more tricky as use flags will effect alot of
> applications.
Stick to the defaults, if people want to change them, they can rebuild.
Reduces our headache, and the problems with dependencies.
>
> as to hosting the binaries ... maybe looking at something like
> bittorrent or other p2p system would be worthwhile looking into (this
> could even be investigated for the current rsync/distfiles system) but
> then hash/md5/etc checking would become very importand.
unfortunately, Bittorrent works best on larger files, due to design, and
it has to be in "constant use" to be worthy.
Gnutella is a viable system, if we change the way the clients work and
hook up. Background daemon to stay connected and share, wide node-splay
and then attempting to reconfigure so each node will "try" to connect to
nodes that have what we want. follow that up with a front-end client to
send download requests from the dameon and theres something that might
work.
No, dont suggest giFT/OpenFT. It doesnt scale anymore:/ Freenet is an
idea, as is gnunetd, but both are laggy protocols, which is rather
negative in our case since people mind speed.
And yes, package signing would be really important for such a case.
//Spider
--
begin .signature
This is a .signature virus! Please copy me into your .signature!
See Microsoft KB Article Q265230 for more information.
end
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-04-10 9:41 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-10 0:13 [gentoo-dev] Binary release of gentoo Noah Justin Norris
2003-04-10 6:28 ` leahcim
2003-04-10 7:03 ` Robert Cole
2003-04-10 8:29 ` Cedric Veilleux
2003-04-10 8:29 ` Jon Portnoy
2003-04-10 8:55 ` leahcim
2003-04-10 9:07 ` Henti Smith
2003-04-10 9:41 ` Spider [this message]
2003-04-10 9:49 ` Henti Smith
2003-04-10 16:30 ` [gentoo-dev] " Peter Simons
2003-04-11 8:14 ` [gentoo-dev] " Miles Egan
2003-04-11 2:01 ` DJ Cozatt
2003-04-11 14:43 ` Dan Armak
2003-04-11 16:11 ` Jon Kent
2003-04-10 10:54 ` Noah Justin Norris
2003-04-10 7:27 ` Spider
2003-04-10 8:13 ` Cedric Veilleux
2003-04-10 8:45 ` Spider
2003-04-11 8:16 ` Miles Egan
2003-04-10 15:52 ` Robin H.Johnson
2003-04-10 18:57 ` Jon Portnoy
2003-04-11 0:51 ` Spider
2003-04-10 8:08 ` Dylan Carlson
2003-04-10 18:50 ` Matt Thrailkill
2003-04-10 19:34 ` Dan Armak
2003-04-10 21:54 ` Mark Farver
2003-04-10 22:17 ` Dan Armak
2003-04-10 23:01 ` Matt Thrailkill
2003-04-11 1:55 ` Terje Kvernes
2003-04-11 14:42 ` Dan Armak
2003-04-11 10:17 ` Noah Justin Norris
2003-04-11 5:48 ` C. Brewer
2003-04-11 4:20 ` John White
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=20030410114139.4ad76a8b.spider@gentoo.org \
--to=spider@gentoo.org \
--cc=gentoo-dev@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