On Wed, Jun 29, 2011 at 3:42 AM, Petr Mladek <pmladek@suse.cz> wrote:
Caolán McNamara píše v Út 28. 06. 2011 v 14:01 +0100:
On Tue, 2011-06-28 at 11:33 +0200, Alexander Thurgood wrote:
Could we not have a "nightly" tag ? Or if we do that, are
we going to have tag overkill like we did with OOo ?
Sounds like a good thing to have a different version than the catch-all
"unspecified", not sure who's got the power to add versions into the
list ? Petr ?
As per the other thread, new dailies should have build-ids in their
about dialog which are useful from a dev perspective to identify what
happens between a good daily and a bad daily, but those change
per-commit of course so best pasted into the body of a daily bug report
as free-form text.
One solutions would be to add something like this to the tinderbox
scripts:
pull_date=`date`
./ pull -r
./autogen
[...]
--with-build-version="Daily built at $pull_date"
Another solution would be to define a default value in the configure.in,
I like that better... the tinderbox rely heavily on autogen.lastrun
right now. tweaking that file on the fly to substitute/add a
date-of-the-day is certainly doable but much more fragile an error
prone than a config-level generated value.
and the later would also be easy to use for the occasional one-shot
manual build.
Norbert
Context
Re: [Libreoffice] Extension manager does not start when dragging extensions from Finder onto main app window - build 350m1 from master nightly 27/06/2011 for Mac OSX · Alexander Thurgood
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.