I am also re-leaning back to being super OK w/ CentOS7. After all, we've already been using it for various 4.2.0-dev builds.
Also, I am not really all that worried about using old, deprecated, EOL platforms *as community build servers*. The goal for those builds is that they support as large and as wide (and as old, reasonably) set of users as possible. So what if the build servers are old... they are just build servers. We aren't running them as anything else. So what if the versions of gcc are old, for example? As long as the binaries produced still run OK on old and new platforms, what's the problem? And again, I am fine with us producing 2 sets of Linux community builds: one for "legacy" users, using CentOS7, and one for "current" users using CentOS8 (or some current flavor of Ubuntu). The latter would, of course, be 64bit only. I don't mind the additional workload if it helps our community. > On Nov 10, 2020, at 5:03 PM, Andrea Pescetti <pesce...@apache.org> wrote: > > Jim Jagielski wrote: >> Cast your vote: >> [X] CentOS7 >> [ ] Ubuntu 14.04 >> [ ] Something else: <enter suggestion here> > > CentOS 7 builds will run under Ubuntu 13.x too. While CentOS 7 32-bit would > be unsupported, the 64-bit version would receive maintenance until 2024; > Ubuntu 14.04, instead, is already unsupported both in 32-bit and 64-bit. > > EPEL unavailability for 32-bit might be an issue though. > > Regards, > Andrea. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
