On 08/08/2016 08:06 AM, Amos Jeffries wrote:
> IMO, eCAP has pretty much stabilized.
We will need a new major eCAP version/release to accommodate
backwards-incompatible C++11 builds as discussed at
http://bugs.squid-cache.org/show_bug.cgi?id=4376#c19
IMO, eCAP has pretty much stabilized.
Any objections to auto-enabling it whenever available?
That would also mean adding it as a builddependency on our farm nodes.
So we can explicitly fail build if eCAP code is overlooked in changes
like rev.14778.
Amos
