Re: wip/pkgchkxx: a complete reimplementation of pkg_chk and pkg_rolling-replace

[Greg Troxel <gdt%lexort.com@localhost>]

Mike Pumford <mpumford%mudcovered.org.uk@localhost> writes:

> In any other language a 3 year old iteration would be considered
> obselete and a 6 year old version would be unusable.

Just because most of the rest of the world doesn't value stability
doesn't make that a good thing.  Rapid changes in things that are
included in base systems is really not ok.  In it's favor, valid C++
programs with older standards tend to still be valid in newer versions.

The software dependency chain is a release of compilers supporting a
standard, when that release is solid enough for production use across
all CPUs, adopting that into a base system, releasing that base system,
and then that system aging out of reasonable support.  Even if you
discount CentOS like things that want to do security updates for 10
years after release which is a year or so after freeze, this chain still
leads to requiring c++11 being ok now, c++14 iffy, and c++17 forcing
people into installing newer compilers.   That would be ok if they  had
ABI compat.