From: ng0 <ng0@libertad.pw>
To: guix-devel@gnu.org
Subject: Re: Fwd: [curl] Re: configure: --with-libidn or --with-libidn2?
Date: Mon, 26 Dec 2016 14:19:16 +0000 [thread overview]
Message-ID: <8760m6lqmz.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <87bmvylrk5.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me>
ng0 <ng0@libertad.pw> writes:
> It seems as if curl can be build with libidn2 now and they have
> addressed the bug which existed for a while. I will check with
> upstream and send in a fix for our curl package once I am sure
> that the old bug has been fixed.
Misinterpretation on my side, and I forgot that I'm read-only on
that list. Is anyone up to date on libidn2 vs libidn, is version
2 now beyond the stage where it does not break anymore on
unicode?
> --
> ♥Ⓐ ng0
> PGP keys and more: https://n0is.noblogs.org/ http://ng0.chaosnet.org
>
>
> Date: Thu, 01 Jan 1970 00:00:00 +0000
>
> On Sat, 24 Dec 2016, Christian Weisgerber wrote:
> MIME-Version: 1.0
> Content-Type: text/plain
>
>> In 7.51.0 and later, the actual configure script option for libidn2
>> is still "--with-libidn", but the help text refers to "--with-libidn2".
>
>> This can be fixed either way, but the inconsistency is confusing.
>
> Oops, yes that seems silly. I think we should switch to --with-libidn2
> completely. I'll fix!
>
> --
>
> / daniel.haxx.se
> -------------------------------------------------------------------
> List admin: https://cool.haxx.se/list/listinfo/curl-library
> Etiquette: https://curl.haxx.se/mail/etiquette.html
--
♥Ⓐ ng0
PGP keys and more: https://n0is.noblogs.org/ http://ng0.chaosnet.org
next prev parent reply other threads:[~2016-12-26 14:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-26 13:59 Fwd: [curl] Re: configure: --with-libidn or --with-libidn2? ng0
2016-12-26 14:19 ` ng0 [this message]
2016-12-26 17:00 ` Leo Famulari
2016-12-26 17:10 ` ng0
2016-12-26 17:35 ` Leo Famulari
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8760m6lqmz.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me \
--to=ng0@libertad.pw \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.