On Mon, Aug 25, 2014 at 11:28 AM, Michael Stahl <mstahl@redhat.com> wrote:
On 25/08/14 09:49, Alex Thurgood wrote:
Absolutely, and I personally agree, but my question is more whether
there is a way for a user of the dailies to easily know what is/isn't in
the build, other than hopefully finding a build.log file also posted on
the relevant page ?
Say I wanted to kitchen sink LO on OSX and provide a TB, how would a
user know from the download page, what was in it ?
that's actually a good point - ideally the upload directory would
contain the autogen.input of the tinderbox so it's immediately obvious
what options were enabled in the build, to not waste time trying to test
something that isn't even enabled.
when using tb to upload dailies, a 'manifest' is uploaded that
contains the needed info and more
see:
http://dev-builds.libreoffice.org/daily/master/MacOSX-x86@49-TDF/2014-08-25_01.28.31/master~2014-08-25_01.28.31_build_info.txt
Norbert
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.