Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


Hi *,

due to legitimate complaints from LibO packagers, I've tweaked the
dir layout of our _archival_ site - *current versions are not
affected*.

The layout collects all artifacts of a given version below the full
numeric version identifier (e.g. 3.4.1.3 for 3.4.1 final), including
boxed and portable version, plus src tarballs:

3.4.1.3
├── box
├── deb
│   ├── x86
│   └── x86_64
├── mac
│   ├── ppc
│   └── x86
├── portable
├── rpm
│   ├── x86
│   └── x86_64
├── src
└── win
    └── x86

Going forward, each mirrored stable release in
http://download.documentfoundation.org/libreoffice/stable will get
linked over to the archival tree already, and every mirrored testing
release will have at least the src tarballs linked there (this is
due to the fact that, from the binary names, we chop the "-rcXY"
part on release - so I can't copy rc binaries to old/, because it
might become the release).

Packagers can now safely use links to this archival tree, without
tarballs moving there anymore from the stable tree.

Cheers,

-- Thorsten

-- 
Unsubscribe instructions: E-mail to website+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/website/
All messages sent to this list will be publicly archived and cannot be deleted

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.