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


Hi Cor,

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

        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.

        Thomas, separately I wonder if this:

INSTALLDIRNAME=`echo AC_PACKAGE_NAME | tr '[[:upper:]]' '[[:lower:]]'`
AC_MSG_CHECKING([for install dirname])
if test -n "$with_install_dirname" -a "$with_install_dirname" != "no" -a "$with_install_dirname" != 
"yes" ; then
   INSTALLDIRNAME="$with_install_dirname"
fi
AC_MSG_RESULT([$INSTALLDIRNAME])
AC_SUBST(INSTALLDIRNAME)

        The with_install_dirname stuff looks redundant - we could prolly hack
some of that out.

        So we might be able to build real RPMs / DEBs that are
parallel-installable for these snapshots.

        HTH,

                Michael.

-- 
michael.meeks@suse.com  <><, Pseudo Engineer, itinerant idiot


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.