On Thu, 2012-04-05 at 17:49 +0200, Lubos Lunak wrote:
So I think it would make sense if we had a special bibisect repository for
master and the stable branch that would be continually updated at reasonable
intervals. I've been told that we should have enough of storage capacity
somewhere, and I was originally going to offer my build machine for this if
needed (it's got nothing to do during the nights anyway, and more than one
rebuild and repack daily probably shouldn't be needed). I have no idea about
the storage requirements of this or the time needed for reasonable repacking,
but if there was a better machine to do this, the better.
Yeah, it'd be cool to have a bibisect repo that's automatically updated
by a bot. Also neat would be to take the various installs generated from
it and get some numbers like change in startup time, install size,
memory foot print of the apps over time.
If 15MB per install is a constant, then daily builds for a year would be
about 5 and a half gigs. Practical numbers ?. Do a different repo per
year to keep each one manageable ?
I guess a 32bit build might be more universally useful rather than a
64bit one. Rewind back to the start of the first successful build in
Bjoern's repo and build from there again ?
C.
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.