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


MR ZenWiz <mrzenwiz@gmail.com> wrote on 2011-02-23 11:46:

On Wed, Feb 23, 2011 at 8:42 AM, Manfred J. Krause
<courrier.oou.fr.mjk@googlemail.com> wrote:

Yes.
"This release is bit-for-bit identical to the 3.3.1 Release Candidate
2, so you don't need to download or reinstall if you have that version
already."
→ Release Notes – LibreOffice 3.3.1 Final (2011-02-23)
<http://www.libreoffice.org/download/release-notes/>


Unfortunately, this also includes the minor detail that the downloaded
tarball, at least for 64 bit deb packages, still has the same
directory name as rc2, so manual intervention is required to do the
install (i.e., that script I posted some time back won't work with
this release because the tarball's name does not match the untarred
directory).

Is a little consistency in the releases too much to ask?
 
Perhaps you know, that 3.3.1-rc2 is identical to 3.3.1 (final). And I
think this is the reason, that all (files, sizes ...) are the same.
And if both versions are the same, why should they compile and package 
all packages for all architetures again only for changing ONE number?

---
Have a nice day.

Joachim (Germany)

-- 
Unsubscribe instructions: E-mail to users+help@libreoffice.org
List archive: http://listarchives.libreoffice.org/www/users/
*** 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.