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


Hi Cor,

On Fri, 2011-08-19 at 12:57 +0200, Cor Nouws wrote:
Sometimes I want to keep a build from master for some longer time.
So I copied the root/install folder to somewhere in my /home.
Initially that worked fine, could start it etc.

        Right - because all the hard-coded paths were pointing back at the
previous version :-)

So either the copied build from master still points to some (simlinked) 
files, that have been changed in a later build.
Or ...?

        There used to be a tool:

        solenv/bin/relocate

        that you could pass the new path too having moved the source tree. It
is -likely- that that is not working -so- wonderfully these days (you'd
prolly need to re-source the new environment and do a new 'make
dev-install' after it).

        But it'd be good to fix that up so it continues working. Clearly if you
do an install with 'ooinstall <path>' that will continue working
~forever [ if you don't link it ] - and doesn't drag around the source
tree either, does that help ?

        ATB,

                Michael.

-- 
 michael.meeks@novell.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.