[squid-dev] g++ 4.8.x and std::regex problems

[Amos Jeffries]

On 25/11/2016 11:50 p.m., Christos Tsantilas wrote:
> Hi all,
> 
>   I have problems to run latest squid-5. The reason looks that it is the
> r14954, which removes old GnuRegex and uses the std::regex API.
> 
> The std::regex supported from gcc-4.9 and latest releases and I am still
> using an gcc-4.8.4 on my kubuntu-14.04 LTS release.
> 

Well the STL docs says GCC 4.9, but there are problems on that version
too. I think GCC 5 is going to be the minimum for Squid-5.

Which is the reason why this regex change was delayed until squid-5.


> OK, I can upgrade to newer OS (currently not without problems), but
> since the end-of-life of ubuntu-14.04 and I suppose other OSes (eg
> debian Wheezy, centos7) are near the 2019 is it legal to stop supporting
> them? A developer which uses latest CentOs as primary system needs to
> recompile gcc-4.9, to continue working.

If you want to look at legality;

Part of the LTS contract is that software feature changes are *not*
done. The clients have chosen to make that a requirement. The OS
distributors have chosen to meet it. Nothing to do with what Squid
Project does in our latest shiny version.

It is actually a bit unreasonable to ask us not to add new features to
the upstream code to prevent breakage in something that was designed
specifically NOT to run those new software versions.

So, if anything it is more likely to be "illegal" to run Squid-5 on
those OS.


Despite the unreasonableness I'm procrastinating as much as I can to
balance the overlap of timelines. But I also have to look at the
projected timing of stable releases. If I stretch it much longer we are
going to have a whole pile of 5-year LTS releases through to 2027
suffering from v3.5 bugs that are already fixed by v4.


> 
> The squid-trunk (or now squid-5) is not running only on developers
> machines, sometimes runs on customers machines they need special
> features or need to test the new features and configurations.

That type of service which IMO can and should be paid for. Even with
open source the "free" only stretches so far. Customers have money,
payment is what makes them "customers".

On the other side, v4 is still in beta so if there is a strong need you
can probably still twist my arm into accepting things there. NO big
things though please as it does need to get stable ASAP. And as usual
TLS/SSL stuff is going back as requested, no twisting needed.

Amos