Re: [gentoo-dev] bittorrent option for downloading files ?

[Spider]

begin  quote
On Thu, 29 May 2003 06:50:23 -0700
Zack Gilburd <zack@×××××××××.com> wrote:

> On Thursday 29 May 2003 06:22, Priit Laes wrote:
> > On Thu, 2003-05-29 at 15:22, Henti Smith wrote:
> > > just a quick thought ...
> > >
> > > would it be viable to add bittorrent support to portage to use
> > > instead of wget etc ?
> > >
> > > Henti
> > >
> > > --
> > > gentoo-dev@g.o mailing list
> >
> > It would be good for live/gamecd's... For packages <50 mb it would
> > consume too much cpu power, because you would have to set up a
> > torrent for every small package out there.
> I'm sure there are less consuming and probably less popular
> protocols/programs out there for p2p file sharing, no?  Also, what
> would the problem be with having a variable in the ebuilds like
> FILE_GET="[bittorrent|wget]" ?

I'd suggest a smarter way of doing this actually. something that:

a) doesnt require change to the .ebuild
b) doesn't require manual maintainance
c) doesn't require server-side CPU /support


something like
FETCHCOMMAND="/usr/bin/gentoo-p2p-thingie ${FILE} ${DESTDIR} \
--fallback-timeout 600 -- \
wget -t 5 --passive-ftp \${URI} -P \${DISTDIR}"


Where gentoo-p2p-thingie will automize the download from some supported
p2p net (gnutella would work decently if we had a background client that
shared distfiles and kept connections, then allowed local "get this
file" commands to download.   A simple "get the most popular file on a
search"  would work, provided we use SHA1 matching only. )


This would then do fallback after 600 seconds to wget. And since the
background daemon keeps sharing the distfiles dir, we would propagate
"new" files on the p2p net.  

using a torrent in this case would require a lot of processess on an
updating machine (torrent wants you to keep the download process running
so it will propagate)

of course, other networks would work, provided the network in its own
scale.


//Spider

-- 
begin  .signature
This is a .signature virus! Please copy me into your .signature!
See Microsoft KB Article Q265230 for more information.
end