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

On Mon, 2011-08-29 at 09:05 +0100, Caolán McNamara wrote:
On Sun, 2011-08-28 at 08:29 -0400, Terrence Enger wrote:
Hello, all.

Now that my system holds more than one build from master, my
small mind is even more subject to confusion than it used to
be.  So, I wonder ...

(*) Is there an easy way to display the build id of
    soffice.bin to the sysout or syserr?

Well, because we use a "continuous" master we're now using git ids as
the build-ids, i.e. the string in help about is derived from

./g -s log -n 1 --pretty=format:%h-

at make dev-install/package generation time

make dev-install in my work directory libo_20110825/ seems
to have changed the result in work directory libo/ too.

You can find that id in the install set in program/setuprc so 

grep buildid install/program/setuprc
should match the output of
./g -s log -n 1 --pretty=format:%h-
if there was no intervening pull

Well, my confusion started after I tried to follow the
instructions "How to Build LibreOffice" > "Multiple Work

The branch argument to git-new-workdir is optional, and I
omitted it.  Maybe I fat-fingered something else.  Or maybe
my expectation was wrong.  Anyway, I was surprised to find
that `git pull` in the new work dir changed the result of
`git branch --verbose` in the previous work directory.

Meanwhile, Regina Henschel has told me a couple of ways I
can make it clear to myself just which soffice I am running.


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.