public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Henti Smith <bain@tcsn.co.za>
To: Spider <spider@gentoo.org>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Binary release of gentoo
Date: Thu, 10 Apr 2003 11:49:49 +0200	[thread overview]
Message-ID: <20030410114949.592f0199.bain@tcsn.co.za> (raw)
In-Reply-To: <20030410114139.4ad76a8b.spider@gentoo.org>

On Thu, 10 Apr 2003 11:41:39 +0200
Spider <spider@gentoo.org> 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 

Because portage downloads files in one dir ... the ebuild can be in that format .. 
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 ... 

but it's just an idea :) 

> > this is logical .. and workable.
> 
> and my idea gives less files to list ;)

but harder to implement in portage .. I can see portgae admins frothing at themouth already about this thread ;P hehehe 

> Stick to the defaults, if people want to change them, they can rebuild.
> Reduces our headache, and  the problems with dependencies.

I agree with that one :) 

> unfortunately, Bittorrent works best on larger files, due to design, and
> it has to be in "constant use"  to be worthy.

I'm not very familiar with it .. so was just a mention :) 

>  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.

This can release alot of load from the distfile mirrors ... and should really be looked at,
esp if one of the mirrors go down etc etc there is another machine with the files availible .. 

> 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.

I'm not very clued up on p2p .. I don't personally use it often if at all, but I think 
distributed system for distfiles can be very successful for gentoo ... for both source and binary systems.

> And yes, package signing would be really important for such a case.

agreed :) 

Henti 

--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-04-10 10:00 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
2003-04-10  9:49             ` Henti Smith [this message]
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=20030410114949.592f0199.bain@tcsn.co.za \
    --to=bain@tcsn.co.za \
    --cc=gentoo-dev@gentoo.org \
    --cc=spider@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