Hi,
Am 13.10.2010 um 10:57 schrieb LKD FTP:
...
On the other hand, feel free to exclude languages that are not
interesting for your mirror / for the region you serve.
[...]
We didn't find the time yet to prepare rsync modules for that --
although that is still planned, as we have all the download statistics
that allow this to be done easily.
Please let me know if there is a problem or we can do something better
for you.
[...]
In OpenOffice, localized builds were under a directory named "localized", so to mirror only a few
languages, the following rsync exclude rules could be used.
"""""
+ /localized/xx/
/localized/*
"""""
I'm not sure yet if we will go that route, or do it in a different way - we are still plugging
everything together to get up and running, and nothing is set in stone; the above is certainly an
option. Even though I don't think that other languages than English should be in a separate
directory (that's only confusing I think). I can imagine a scheme like releases/$version/$lang/...
for instance, which avoid different file trees for English vs. non-English.
Can a similar scheme be used for LibreOffice? To add, if the rsync modules for languages are to
be prepared soon, this issue would be non-existing.
We are indeed working on it!
Peter
--
To unsubscribe, e-mail to mirrors+help@documentfoundation.org
All messages you send to this list will be publicly archived and cannot be deleted.
List archives are available at http://www.documentfoundation.org/lists/mirrors/
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.