<div dir="ltr">And, a lot of the the tools using mirrors are generally addressed to a fairly technical community. The other big difference is obviously that the linux community is massive, and we are small in comparison. But I'm all up for more resilience if that's something we've had an issue with?</div>
<div class="gmail_extra"><br><br><div class="gmail_quote">On 4 January 2013 21:58, DM Smith <span dir="ltr"><<a href="mailto:dmsmith@crosswire.org" target="_blank">dmsmith@crosswire.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Regarding Fedora, I find that the mirrors differ significantly. Some have old releases, but no new releases. Some have the latest release but no updates. Some may have the alphas and/or the betas. Using yum, I have had some updates fail because they have dependencies that have not reached the mirrors that yum wants to use, making me wait a few days until the mirrors catch up. Adding in unofficial repositories complicates it even more.<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
<br>
On Jan 4, 2013, at 4:18 PM, Greg Hellings <<a href="mailto:greg.hellings@gmail.com">greg.hellings@gmail.com</a>> wrote:<br>
<br>
> On Fri, Jan 4, 2013 at 3:06 PM, DM Smith <<a href="mailto:dmsmith@crosswire.org">dmsmith@crosswire.org</a>> wrote:<br>
>> If someone posts to sword-support a problem with the text in a module (we<br>
>> get these all the time), having mirrors complicates support.<br>
><br>
> If Fedora can have many dozen mirrors, and Debian can have many dozen<br>
> mirrors and so can every Linux distribution out there, is it so hard<br>
> for us to have mirrors when it comes down to it? Each of these has<br>
> requirements for what a mirror MUST, SHOULD and MAY provide and they<br>
> have a vetting process when someone wants to become an official mirror<br>
> they ensure that the offer follows those requirements.<br>
><br>
> For the most part those requirements boil down to: provide the<br>
> mandatory parts of the distribution with the same layout they have on<br>
> the master, and update at minimum every X hours or days. That's hardly<br>
> a burdensome task to setup, consisting mostly of a handful of options<br>
> to something like rsync. If we wanted to have official mirrors we<br>
> could be sure anyone offering followed those requirements and then add<br>
> them to a master list of mirrors. It's not that complicated to require<br>
> and it's not that complicated to configure. Many people offering to<br>
> setup mirrors would already be familiar with the methods and<br>
> requirements.<br>
><br>
> Yes, licensing would still be an entirely different issue, but the<br>
> technical implications of offering a mirror system for a pure list of<br>
> files is not difficult. And certainly it's not more difficult than<br>
> offering ISO images for users to download and encouraging them to be<br>
> able to share them with friends!<br>
><br>
> --Greg<br>
><br>
> _______________________________________________<br>
> sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>
> <a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
> Instructions to unsubscribe/change your settings at above page<br>
<br>
<br>
_______________________________________________<br>
sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at above page<br>
</div></div></blockquote></div><br></div>