Oh, I see ... thanks Kay for the link.
Ariel's two reasons are:
"a) Centos 5 will get Maintenance Updates until March 31st, 2017"
" b) this change should be done in a major version change, as it breaks
compatibility in client code".
About (a) .. Full updates ran off at Q1 2014. Does this mean we would have
to limit to whatever is supported by gcc 4.1 + libsdc++ 4.1 ?
About (b) I disagree we should change our numbering just because an OS
vendor released a new version. At least we don't do that every time
Microsoft
or MacOSX releases a new version. Do we still do our builds in WinXP?
I guess we could still provide CentOS5 in the packages for the few users
this has,
but it is important to start upgrading the reference CentOS (and other
linux versions).
My main concern is that with the removal of stlport we are depending
more on the native
STL and boost. Newer boost versions are already dropping support for older
versions of gcc and gcc 4.1 is not tested anymore.
We can leave the codebase untouched for compatibility but the
dependencies won't
wait for us (or CentOS). And then ... I am considering starting my own
branch and
drop all remnants of backwards compatibility, but then I could just drop
linux altogether
as I don't test it and we don't have buildbots for branches :-P.
Pedro.
On 05/30/15 15:57, Pedro Giffuni wrote:
Hello;
I started the discussion on dropping CentOS 5 and moving on
to CentOS 6. There was no comment against moving to the
newer version, which AFAICT is the last version to support
32 bits.
Assuming AOO builds on CentOS 6, is there any reason to insist
on CentOS 5?
Pedro.
