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

MacPorts noreply at macports.org
Thu Jul 29 21:42:57 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 ryandesign):

 Replying to [comment:7 RJVB]:
 > 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.

 If they were truly drop-in replacements, yeah.

 > > 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,

 I have no idea.

 > and how feasible would it be to "backport" this function to libidn2
 (possibly as an additional, preferably static library)?

 I would not consider it our job to do such a thing. The developers of
 libidn2 could do that if they felt it appropriate.

 > 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.

 Agreed. I was just attempting to follow up on the suggestion of the
 reporter.

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

 According to Ghostscript's configure.ac file: `dnl Check for libidn
 (needed for Unicode password support)`

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


More information about the macports-tickets mailing list