1.12.3 library versioning

[Andreas Metzler]

Hello,

1.12.3's NEWS says:
   - Due to the minor API updates and but with no newer branch
     released the SO name has been updated.

On linux we went from libgcrypt.so.20.7.2 to libgcrypt.so.20.8.8 which
seemed strange. Looking at configure.ac we find:
8x-------------------------------------------------------
 # LT Version numbers, remember to change them just *before* a release.
 #   (Code changed:			REVISION++)
 #   (Interfaces added/removed/changed:	CURRENT++, REVISION=0)
 #   (Interfaces added:			AGE++)
 #   (Interfaces removed:		AGE=0)
 #
 #   (Interfaces removed:    CURRENT++, AGE=0, REVISION=0)
 #   (Interfaces added:      CURRENT++, AGE++, REVISION=0)
 #   (No interfaces changed:                   REVISION++)
-LIBGCRYPT_LT_CURRENT=27
-LIBGCRYPT_LT_AGE=7
-LIBGCRYPT_LT_REVISION=2
+LIBGCRYPT_LT_CURRENT=28
+LIBGCRYPT_LT_AGE=8
+LIBGCRYPT_LT_REVISION=8
8x-------------------------------------------------------

Using LT versioning we should have gone from LC=27 LA=7 LR=2 to one of
* LC=27 LA=7 LR=3 (code changed, interface unchanged)
* LC=28 LA=8 LR=0 (Interfaces added, none removed)
* LC=28 LA=0 LR=0 (Interfaces removed, none removed)
instead of LC=28 LA=8 LR=8 (Interfaces added, none removed, followed by
8 releases without ABI changes.)

I guess LR=8 was a typo but I wanted to doublecheck whether I am missing
something.

I do not propose to switching to LR=0, not jumping backward in
versioning is better than fixing a very minor cosmetic thingy.

thanks, cu Andreas

-- 
"You people are noisy," Nia said.
I made the gesture of agreement.