Opened 7 years ago
Closed 7 years ago
#9045 closed enhancement (fixed)
Add libidn2 to the book
Reported by: | Richard Melville | Owned by: | Douglas R. Reno |
---|---|---|---|
Priority: | normal | Milestone: | 8.2 |
Component: | BOOK | Version: | SVN |
Severity: | normal | Keywords: | Suggestion |
Cc: |
Description (last modified by )
Download (HTTP): https://ftp.gnu.org/gnu/libidn/libidn2-2.0.3.tar.gz Download (FTP) : ftp://ftp.gnu.org/gnu/libidn/libidn2-2.0.3.tar.gz
Build - this worked for me:-
./configure --prefix=/usr --disable-static --docdir=/usr/share/doc/libidn2-2.0.3
Change History (16)
comment:1 by , 7 years ago
comment:2 by , 7 years ago
From the libidn web page:-
"Please be aware that GNU libidn2 is the successor of GNU libidn. It comes with IDNA 2008 and TR46 implementation and also provides a compatibility layer for GNU libidn."
In addition, GnuTLS will build with libidn2 support but NOT with libidn support.
One caveat: For some reason my build of libidn2 did not provide a .pc file. I haven't had the opportunity yet to find out why that was the case.
Finally, we have pages for both NASM and Yasm which, IMO, is a similar situation.
comment:3 by , 7 years ago
Have you tried to build all the packages in my previous comment? If we can get by with only one package, either the old or the new, then that's what I want to do. Right now we don't *need* libidn2.
We do have several places where we still have multiple versions in the book. ImageMagick for one. We had qt4 and qt5 before, but removed qt4 as soon as we could. I'd like to put back amarok, but it is still qt4 only. We also used to have two versions of webkitgtk, but are now down to one.
comment:4 by , 7 years ago
Packages in previous comment that can be built with libidn2 support:-
Systemd - not sure Wget - yes (from 1.19.1) Mutt - no Whois - yes GnuTLS - yes Gs - no Exim - yes Pidgin - not sure but Jabber supports libidn2
comment:5 by , 7 years ago
Wget2 is an updated version of wget: https://github.com/rockdaboot/wget2
comment:6 by , 7 years ago
Milestone: | 8.1 → hold |
---|---|
Summary: | Suggesting a new page entry in the book for libidn2 → Add libidn2 to the book (wait for systemd to suppor it) |
Changing title and moving the ticket to hold until at least systemd supports it.
For mutt, gs, and pidgin, the dependencies are all optional and we can make the current libidn an external dependency. I do not want to have both libidn and libidn2 in the book at the same time.
comment:7 by , 7 years ago
https://github.com/systemd/systemd/pull/5928
So it begins. Oh yes, curl is missing from the list above. It, too, doesn't support old libidn anymore, only libidn2.
comment:9 by , 7 years ago
Milestone: | y-hold → 8.1 |
---|
systemd-234 is out, with libidn2 support (which is marked experimental).
comment:10 by , 7 years ago
See http://www.theregister.co.uk/2017/07/24/underscore_domain_name_bug/
Perhaps we should wait.
comment:11 by , 7 years ago
This is fixed in libidn-2.0.3, bug is here: https://gitlab.com/libidn/libidn2/issues/30 and fix is here: https://gitlab.com/libidn/libidn2/commit/05d753ea69e2308cd02436d0511f4b844071dc79
Although systemd-resolvd should work with 2.0.3, they wrapped it in a test case here to make sure conversion to and from matchl (and if not, punt): https://github.com/keszybz/systemd/commit/a5971c34ac2693f22af84b79ca923307ac72b927 This shouldn't be necessary, and shouldn't affect lookups if there are no extended chars, but I haven't tested libidn2 yet.
comment:13 by , 7 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:14 by , 7 years ago
Description: | modified (diff) |
---|---|
Summary: | Add libidn2 to the book (wait for systemd to suppor it) → Add libidn2 to the book |
comment:15 by , 7 years ago
Milestone: | 8.1 → 8.2 |
---|
comment:16 by , 7 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Added libidn2 to the book at r19249
I'm not sure what this adds. It can optionally be used in gnutls, but libidn (not libidn2) is used in the following:
What does libidn2 offer that we don't have?