abseil v20230125 LTS

[h-vetinari]

Seems the bot didn't pick this one up.

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

[njzjz]

#error "C++ versions less than C++14 are not supported."

[h-vetinari]

#error "C++ versions less than C++14 are not supported."

Yeah, I know, I just forgot to drop them. However, there's some more libs that haven't been properly taken care of on the windows DLL side which I'm just looking into.

[h-vetinari]

@conda-forge/abseil-cpp
This should be good to go. A bunch of patches were upstreamed successfully (with the exception of abseil/abseil-cpp#1115 that's yet to be merged), otherwise this is a pretty standard version bump.

Of course, dropping C++11 raises the question if we should even keep building C++14 and the respective static libs. To the best of my knowledge, all feedstocks in cond-aforge depending on abseil are now on C++17, so arguably this isn't necessary anymore. On the other hand, we haven't fixed the situation with #45 yet, which will only get dicier now that protobuf has started depending on abseil.

So far there shouldn't be many (relevant) ABI differences between C++17 and C++20, but those will very likely arise over time.

CC @conda-forge/core @conda-forge/libprotobuf @coryan @pitrou @rgommers

[h-vetinari]

Ah yes, and I wanted to remove the compatibility output for the old name abseil-cpp. Based on this search it's not depended upon by a feedstock in conda-forge anymore.

[xhochy]

Removal of the abseil-cpp output seems fine.

[h-vetinari]

On further reflection, I decided to remove the libabseil-static outputs. They did not fulfill their intended role as encapsulating the ABI concerns, and are not in use anywhere AFAIK. They can of course be readded if ever the need arises.

Barring further comments, I'll merge this in 24h.