[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: providing a libidn compatibility API
From: |
Nikos Mavrogiannopoulos |
Subject: |
Re: providing a libidn compatibility API |
Date: |
Mon, 20 Feb 2017 11:58:49 +0100 |
On Sun, Feb 19, 2017 at 10:14 AM, Simon Josefsson <address@hidden> wrote:
>> I'd expect the idna2003 + idna2008 apps to be rare, but you got a
>> point. I think the define approach is reasonable.
> Agreed.
> In practice I believe we will see significant number of applications
> that will link to both libraries because of indirect dependencies. It
> will easily take 5-10 years before applications stop link to libidn in
> the supported released GNU/Linux distributions.
I've pushed a merge request documenting the changes in libidn2 0.17:
https://gitlab.com/jas/libidn2/merge_requests/8
Hopefully that can be the first release that we can use to initiate a
migration from libidn1.
regards,
Nikos
- Re: providing a libidn compatibility API, (continued)
- Re: providing a libidn compatibility API, Nikos Mavrogiannopoulos, 2017/02/10
- Re: providing a libidn compatibility API, Tim Rühsen, 2017/02/10
- Re: providing a libidn compatibility API, Nikos Mavrogiannopoulos, 2017/02/13
- Re: providing a libidn compatibility API, Nikos Mavrogiannopoulos, 2017/02/14
- Re: providing a libidn compatibility API, Tim Ruehsen, 2017/02/14
- Re: providing a libidn compatibility API, Nikos Mavrogiannopoulos, 2017/02/14
- Re: providing a libidn compatibility API, Simon Josefsson, 2017/02/19
Re: providing a libidn compatibility API, Simon Josefsson, 2017/02/19
Re: providing a libidn compatibility API, Simon Josefsson, 2017/02/19
- Re: providing a libidn compatibility API,
Nikos Mavrogiannopoulos <=
Re: providing a libidn compatibility API, Simon Josefsson, 2017/02/19