#63329 closed enhancement (duplicate)
p5.30-io-socket-ssl depends via p5.30-net-libidn from libidn while libidn2 is out
Reported by: | ballapete (Peter "Pete" Dyballa) | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.7.1 |
Keywords: | Cc: | ||
Port: | p5-io-socket-ssl |
Description
libidn2
(@2.3.2) is installed and already used by some ports. ghostscript
and p5.30-net-libidn
are the last two that depend on libidn
(@1.38) and not libidn2
, the latter exists only because p5.30-io-socket-ssl
depends on it instead of libidn2
.
Is there a reason for this (old, traditional) dependency?
Change History (2)
comment:1 follow-up: 2 Changed 3 years ago by jmroot (Joshua Root)
Port: | p5-io-socket-ssl added; p5.30-io-socket-ssl removed |
---|---|
Resolution: | → duplicate |
Status: | new → closed |
comment:2 Changed 3 years ago by ballapete (Peter "Pete" Dyballa)
Note: See
TracTickets for help on using
tickets.
It probably makes sense to handle this as part of #63309.