While doing testing with 13.0-BETA4 I see libidn2-2.3.0_1 exists
but libidn-1.35 is still around. Just a thought that is could be
UNIX and Linux spoken
GreyBeard and suspenders optional
Did this die or just not worth revving up to 1.36 or maybe 1.37 ?
I spot 45 ports which use libidn-1.35,
but I wonder how many truly require the old lib (instead of libidn2).
Created attachment 226387 [details]
This patch is simpel version upgrade (plus I've adjusted the patches).
And I've changed the order in Makefile (on demand of portfmt & portclippy).
Tested all fine with portlint, poudriere, portfmt, portclippy.
(In reply to Leo Vandewoestijne from comment #3)
Looks perfect. Should work just fine and yes I see there are ports that
still want the previous rev library ( as opposed to libidn2 ) and to be
fair this is a trivial matter not even worth thinking about. I have
never had problems with libidn or libidn2 even on strange systems. Just
release it and let the other port maintainers do what they do.
I agree we can just bump libidn to 1.37. The patch looks good to me.