Since upstream clearly doesn't care about binary compatibility at all, I don't see a reason to keep SONAME in sync with them. Therefore, please bump SONAME whenever the version bump introduces ABI-incompatible changes. Otherwise, our users end up with broken Chromium for a few hours after re2 upgrade. In order to avoid potential collisions in case upstream got some sanity one day, you can go for branded sonames like .so.1g or so.
Hmm... I guess that's a reasonable compromise. I'll revbump it, unless there is some objection to that?
SGTM, please go ahead.
commit bac5b508817eba3b6f91c7340cc1db777ff6ee84 Author: Mike Gilbert <floppym@gentoo.org> Date: Tue Dec 27 22:53:52 2016 -0500 dev-libs/re2: override SONAME Upstream does not seem to maintain any sort of binary compatibility, so implement our own naming scheme. Bug: https://bugs.gentoo.org/603824 Package-Manager: Portage-2.3.3_p9, Repoman-2.3.1_p2 .../{re2-0.2016.11.01.ebuild => re2-0.2016.11.01-r1.ebuild} | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-)
