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


On Tue, Jun 4, 2019 at 5:01 PM Luke Benes <lukebenes@hotmail.com> wrote:

The decision was to demote release builds, but NOT to remove x86 compatibility. If you take this 
as an excuse to also end x86 CI testing bots, you are effectively killing x86 through bit rot.

That is completely missing the point. The tinderbox *IS* using
baseline. And since the baseline is not recent enough to build 32bit
anymore, there is *no way* to have it still produce builds. Otherwise
32bit binaries could still be provided.

This is not a hypothetical. As you know, @87 just recently caught a regression […]

Anyone is free to setup a tinderbox and send results - no registration
or similar needed for that,
https://wiki.documentfoundation.org/Development/Tinderbox/Setup

If we chose to go down the path of killing x86, we should discuss it. While I agree that overhead 
of x86 release build may not be worth it, the advantages of maintaining a working x86 build are 
clear.  My suggestion would be to upgrade @87 to CentOS 7 or Debian 9.0 before bit rot makes this 
a difficult task. Currently master has no problem building on 32-bit Fedora 30.

My personal interest is having baseline builds verified. So there is
no point if the build succeeds in a current distro, but cannot run on
the end-users systems because of glibc or other requirements.

But again: anyone can setup a tinderbox...

ciao
Christian

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.