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

On 07/18/2011 05:12 PM, Robert Boehm wrote:
On 07/18/2011 07:04 PM, plino wrote:
Robert Boehm wrote:
Obviously, if the version "preferred" by the installer is the only
version that the installed files will work with
is the only choice, then well, OK.  But if it's compatible with the
latest version, maybe there is a way to make
sure that the latest version available is installed (that is compatible)
rather than whatever it was built with....
but I am ignorant as to if this is feasible or not....or if testing is
available to make sure that this works.

I have uninstalled the version bundled with LibO and kept the newer version.
All is working as expected because updates to VC++ 2008 are security and bug
Good....a work-around....thanks.

Not necessarily as LO is installing a version with security issues & IMO
that needs to be resolved. The standard 'user' won't know to uninstall
the bundled version as plino did. This is similar to when OOo installed
insecure versions of java et al. The user would then have parallel
versions of jave installed.

I'd recommend a followup to the dev list. plino, when you do that you
might also add links to the security notices for the earlier version of
VC++ 2008.

Unsubscribe instructions: E-mail to
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.