Re: Failure with libidn2 on OpenBSD.

[Mats Erik Andersson]

Måndag den 25:e januari 2021, klockan 08:47, skrev simon--- via Bug reports for 
the GNU Internet utilities detta:
> Indeed, on a modern system with glibc, everything works via getaddrinfo
> without need to link with libidn/libidn2.  The code in inetutils is
> buggy today (it passes on non-domains to IDNA functions), and if anyone
> wants IDN-enabled applications on non-GNU systems, the best place to fix
> this would be in gnulib's getaddrinfo.  Then it would work automatically
> in inetutils too.  Fixing the bugs and supporting the build complexity
> just to cater for non-GNU platforms is not worth the maintainence cost
> for us, IMHO.
> 
> Given the discussion above, I propose to remove all uses of
> libidn/libidn2 from inetutils, and place a note in gnulib's getaddrinfo
> that it is missing IDN-functionality to mimic glibc's IDN behaviour.  I
> might even get around to adding IDN-functionality to gnulib, but no
> promises.
> 
> Any objections?  I'll test the rest of the apps in InetUtils and remove
> this code if there aren't any objections.

As can be expected, I do object to the removal of our IDN-code, as long
as no other provider of the corresponding functionality is present.
My Sisyphos task of keeping Inetutils useful beyond glibc-systems is
truely a never ending mission, expected to last until my demise or to
my retirement, whichever comes first.

Why is the action simply to disable IDN-linkage for glibc-systems so
repulsive that you want to cripple all other users?

Regards,

  M E Andersson