Date: prev next · Thread: first prev next last




--On lördag, mars 19, 2011 11.08.43 +0800 Elton Chung <elton@elton.tk> wrote:

Hi all,
I am now being a mirror provider of LibreOffice, but I would just
like to know why we are not using SourceForge as part of our
downloading mirrors? AFAIK the latest version of LibO on SF is 3.3.0
and a link is pointing to libreoffice.org.
Although we have more than 40 mirrors currently, we still don't have
mirrors in Taiwan, UK, Australia, Russia.
And SF provides mirrors from these countries.
Could using SF provide better downloading speed of LibO in these
areas? Or is it impossible to use SF?

Regards,
Elton

--

Hi all!

One bad thing with pushing things through SF is that some mirrors,
mine included, carries both LO and SF (among many other).  So while
it may (or may not, I don't know) provide a benefit in some cases it
also caries the burden of duplicated files for such mirrors.

Now, 10GB on its own isn't to bad, but there are other projects too.
Then you copy it a couple of times for Debian, a few for RH, a few
for Suse, a bunch of other distros and...

Enough ranting:-)  I just wanted to point out that sometimes there
are effects that may not be obvious.  Pushing things through SF can
be one.

Best regards,
       Emil






--
Unsubscribe instructions: E-mail to mirrors+help@documentfoundation.org
List archive: http://listarchives.documentfoundation.org/www/mirrors/
*** All posts to this list are publicly archived for eternity ***

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.