Automated Mirror Selection [Re: Worst experience with Up2Date ever.]

Jeff Spaleta jspaleta at gmail.com
Thu Sep 30 18:14:23 UTC 2004


On Thu, 30 Sep 2004 12:46:15 -0500, Andrew W. Donoho <awd at ddg.com> wrote:
> This will require some scripting on the Redhat side of the repository
> but it is something they fully control - yum, up2date, Fedora
> Distribution, Rawhide update policies. I think this meets all or most
> of Mr. Spaleta's constraints and provides benefits to Redhat and users.

<point and laugh mode>
HeHe you said torrent HeHe
</point and laugh mode>

Constraint one... the mirror system is not a p2p network. That
constraint was aimed directly at anyone suggesting bittorrent as a way
forward.

I frankly don't care much about how well rawhide works. I  believe
everything about rawhide from how packages are pushed to the main
server to how people access mirrors is inherently unstable, fragile
and prone to breaking.  Testers using rawhide should expect breakage
and be prepared for it.  Building any service meant primarily to
satify the demands of access to rawhide is a waste of development
manhours.

I care far far more about finding a way to give each client computer a
way to get a reasonable accurate list of mirrors that works well and
reliably for access to released updates and base packages for full
releases. If discussion isn't framed around this being the central
goal, I'm not overly interested in it.

-jef"hehe rawhide torrent hehe..thats a good one"spaleta




More information about the fedora-test-list mailing list