[MacPorts] #63309: Dependency libidn could be replaced by libidn2
MacPorts
noreply at macports.org
Fri Jul 30 08:36:51 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:8 ryandesign]:
> > 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.
Not intending to start a debate here, so long story short, the same could
be said about the backport of OpenSSL 1.1 support to Qt4, or even the
whole `port:legacy-support`. Or indeed to patching the code to use libidn2
instead of libidn ;)
In that light, what do we do with this ticket now? Is there any reason to
patch code to use libidn2 instead of libidn if we're going to be keeping
both versions anyway?
--
Ticket URL: <https://trac.macports.org/ticket/63309#comment:9>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list