On Sun, 4 Mar 2012 02:54:47 +0000 (UTC)
Alex Elsayed <[email protected]> wrote:

> In thinking about how downloading distfiles currently works, I had an
> idea that might improve the situation as it stands.
> 
> In the past, Paludis has had requests to support BitTorrent for
> distfiles for a variety of reasons. Some of these made sense; some did
> not.
> 
> I'm going to suggest a full revamp of how fetchers work to make the
> entire system more flexible.
> 
...

Instead of implementing more complex fetch logic in paludis, won't it
make sense to follow checksums.exlib and scm.exlib example and just
implement any fetcher extensions there?

It won't work in a separate (from compilation) thread as it does with
current (non-scm) fetchers, but it already isn't async for scm exheres
and checksum verifications.
And fetching from stuff like bittorrent in general will greatly benefit
from being parallel for all distfiles needed, because time to bootstrap
download from a magnet link should be longer than to find a mirror and
download the whole file from there.

Performance aside, having bittorrent fetcher as exlib can have a
benefit that sha1 hash, currently passed only to for checksum.exlib,
can be used to produce a magnet link as well, so all exherbo users can
be used as an "exherbo mirror network", provided the link will be passed
to some long-running daemon (like transmission), not oneshot leecher.


-- 
Mike Kazantsev // fraggod.net

Attachment: signature.asc
Description: PGP signature

_______________________________________________
Exherbo-dev mailing list
[email protected]
http://lists.exherbo.org/mailman/listinfo/exherbo-dev

Reply via email to