[MacPorts] #63309: Dependency libidn could be replaced by libidn2

MacPorts noreply at macports.org
Thu Jul 29 14:32:36 UTC 2021


#63309: Dependency libidn could be replaced by libidn2
-------------------------------------------------+-------------------------
  Reporter:  ednl                                |      Owner:  (none)
      Type:  update                              |     Status:  new
  Priority:  Normal                              |  Milestone:
 Component:  ports                               |    Version:  2.7.1
Resolution:                                      |   Keywords:
      Port:  cpuminer echoping elinks-devel      |
  FileZilla finch ghostscript gloox html-xml-    |
  utils hydra Io jabber jabberd knot kopete      |
  libgsasl libpurple libVLC2 loudmouth lynx      |
  maildrop monotone monotone-devel mutt p5-net-  |
  libidn pidgin podofo prosody psi skipfish tin  |
  VLC2                                           |
-------------------------------------------------+-------------------------

Comment (by RJVB):

 Replying to [comment:3 ryandesign]:

 > Ideally, each software package that currently uses libidn should be
 updated by its developers to support libidn2 without us needing to patch
 it

 Were it not for the below, it would have been perfectly possible to
 install a shim `libidn.h` file that links to or includes `libidn2.h`, idem
 for a `libidn.pc` file that contains the libidn2 settings.

 > Replying to [comment:2 ryandesign]:
 > > * libgsasl
 >
 > Upstream says using libidn2 is not possible because libgsasl requires
 `stringprep`, a function which no longer exists in libidn2:
 https://lists.gnu.org/archive/html/help-gsasl/2021-05/msg00001.html
 ...
 > So for libgsasl at least, and possibly for other ports that might
 require `stringprep`, we cannot remove libidn or migrate them to libidn2.

 Is that the only thing missing, and how feasible would it be to "backport"
 this function to libidn2 (possibly as an additional, preferably static
 library)?

 That said, libidn* aren't the smallest packages around but they aren't
 exactly huge either, and not mutually exclusive. IOW, no hard reason to
 retire libidn.


 PS: why would a PostScript interpreter need an Internet Domain Name
 library?

-- 
Ticket URL: <https://trac.macports.org/ticket/63309#comment:7>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list