I'm skipping the review of src:libnet-idn-encode-perl for now, as I think this would be duplicated functionality in 'main'.
libmail-dmarc-perl seems to be using the "domain_to_unicode" function primarily: lib/Mail/DMARC/Base.pm:use Net::IDN::Encode qw/domain_to_unicode/;
While we already have src:libnet-libidn-perl in "main", providing similar (same?) functionality, through GNU libidn bindings: https://metacpan.org/pod/Net::LibIDN#Net::LibIDN::idn_to_unicode($idn_hostname,-[$charset,-[$flags]]);
Have you considered using this module instead of "libnet-idn-encode-perl", which seems to be a pure perl implementation of similar functionality?
For reference, please also see bug #2003076 as an upgrade path to libnet-libidn2-perl in the future.
I'm skipping the review of src:libnet- idn-encode- perl for now, as I think this would be duplicated functionality in 'main'.
libmail-dmarc-perl seems to be using the "domain_to_unicode" function primarily: DMARC/Base. pm:use Net::IDN::Encode qw/domain_ to_unicode/ ;
lib/Mail/
While we already have src:libnet- libidn- perl in "main", providing similar (same?) functionality, through GNU libidn bindings: /metacpan. org/pod/ Net::LibIDN# Net::LibIDN: :idn_to_ unicode( $idn_hostname, -[$charset, -[$flags] ]);
https:/
Have you considered using this module instead of "libnet- idn-encode- perl", which seems to be a pure perl implementation of similar functionality?
For reference, please also see bug #2003076 as an upgrade path to libnet-libidn2-perl in the future.