[prev in list] [next in list] [prev in thread] [next in thread]
List: macports-tickets
Subject: Re: [MacPorts] #63309: Dependency libidn could be replaced by libidn2
From: "MacPorts" <noreply () macports ! org>
Date: 2021-07-31 9:32:44
Message-ID: 056.d48bb3d3a7ecdcd5510798670471cce7 () macports ! org
[Download RAW message or body]
--===============9064775894592142718==
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
#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:11 ryandesign]:
> Since libidn's IDN processing is based on the obsolete IDN2003 standard,
and libidn2 exists to cover the newer IDN2008 standard
Sounds to me like a case of "no user serviceable parts inside" (aka
fingers off) if you have no idea what that means and/or if you don't know
exactly what your port uses the library for (including possible side-
effects the code turns out to rely on)...
(And I'd use a similar consideration before reporting the use of an old
version of a standard as a bug.)
-- =
Ticket URL: <https://trac.macports.org/ticket/63309#comment:12>
MacPorts <https://www.macports.org/>
Ports system for macOS
--===============9064775894592142718==--
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic