Hi *,
On Mon, Nov 7, 2011 at 12:57 PM, Michael Meeks <michael.meeks@suse.com> wrote:
On Sat, 2011-11-05 at 16:50 +0100, Cor Nouws wrote:
Just tried to install the daily build from 2011-11-02 on my Ubuntu:
http://dev-builds.libreoffice.org/daily/Linux_x86_Release_Configuration/master/2011-11-05_01.05.12/
As this keeps coming back, I was amazed to read:
I install the builds in parallel:
http://wiki.documentfoundation.org/Installing_in_parallel
To install the dev-snapshots, those that are labeled as LibO-Dev-…,
there is no need to go into the manual extraction procedure.
The LibO-Dev buidls will install alongside the stable versions,
without interfering with each other. That's the whole point of that
branding. (i.e. using both different installation directories and also
a different user-profile directory)
You only need to go through manual unpacking or rebasing procedures
when trying to install different versions of the same "flavor", i.e.
when installing multiple LibO-Dev builds or when you want to have
3.4.2 alongside 3.4.3
It looks (potentially) highly problematic. I suggest we add a big
health warning to it.
It would (perhaps) be easier to change the install prefix and/or
installname for our tinderbox builds. I wonder if there is an easy way
to do that (Fridrich?) so we could just install the packages as-is.
This is already the case. Again the whole point of the LibO-Dev
branding/variant.
ciao
Christian
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.