"
Subject: Re: [webkit-dev] Introducing a minimum ICU version for WebKit
Please note that Per Arne updated the Apple ZIP files to have the correctly
aligned ICU libraries, so the Windows bots should have what they need.
I apologize for taking so long to complete that.
Thanks,
-Brent
On
Please note that Per Arne updated the Apple ZIP files to have the correctly
aligned ICU libraries, so the Windows bots should have what they need.
I apologize for taking so long to complete that.
Thanks,
-Brent
> On Apr 3, 2020, at 4:57 PM, Ryosuke Niwa wrote:
>
>
> On Fri, Apr 3, 2020 at 4
>Also, sadly ICU does not maintain a stable API or ABI. So every
>application and library using ICU would need to be rebuilt and updated
>at the same time. Then the update would break any custom software that
>users have using the system ICU. Such an update would go badly...
>probably would win
On Thu, Apr 9, 2020 at 2:48 pm, Michael Catanzaro
wrote:
Sometimes distros make exceptions (e.g. for WebKitGTK, which is
special due to very high number of CVEs), but ICU does not warrant an
exception. There are probably hundreds of applications using ICU in
distros, if not more. Who knows wha
On Thu, Apr 9, 2020 at 7:08 pm, "Olmstead, Don"
wrote:
Hi Michael,
There are a couple problems with checking in a version of ICU.
* Other libraries used by WebKit have dependencies on ICU. For our
ports harfbuzz, libxml2, libxslt, libpsl and CFlite all require ICU.
You're right, it's a
On Thu, Apr 9, 2020 at 11:49 am, Alexey Proskuryakov
wrote:
The license is not BSD or LGPL, so that's one aspect to consider.
Why exactly are distros unwilling to update ICU?
- Alexey
Distros would upgrade to newer minor releases of the library, but
updating system packages to new major
e are better ways for us to approach the requirements that would be
beneficial to all ports?
-Original Message-
From: webkit-dev On Behalf Of Michael
Catanzaro
Sent: Thursday, April 9, 2020 10:32 AM
To: Kirsling, Ross
Cc: webkit-dev@lists.webkit.org
Subject: Re: [webkit-dev] Introducin
Here’s my take:
The source code we check into the WebKit repository is there for the
convenience of the people *contributing* to WebKit, and is need not be the sole
input when building and packaging WebKit for distribution.
Including ICU sources in a GTK WebKit tarball would not necessarily req
The license is not BSD or LGPL, so that's one aspect to consider.
Why exactly are distros unwilling to update ICU?
- Alexey
> 9 апр. 2020 г., в 10:32 AM, Michael Catanzaro
> написал(а):
>
>
> Any objections to uploading a bundled ICU 60 under Source/ThirdParty?
>
> Seems easier than forci
Any objections to uploading a bundled ICU 60 under Source/ThirdParty?
Seems easier than forcing downstreams to work out bundling themselves.
Most major distros will just stop providing WebKit security updates if
we don't bundle it for them. E.g. this is sure to kill Ubuntu's current
long str
On Fri, Apr 3, 2020 at 4:25 PM Kirsling, Ross
wrote:
> Hi everybody,
>
>
>
> Just sending out an email blast for visibility regarding
> https://bugs.webkit.org/show_bug.cgi?id=209694.
>
>
>
> This patch:
>
>- Upgrades the Mac ICU headers under Source/WTF/icu from ICU 55 to ICU
>62, matchi
Hi everybody,
Just sending out an email blast for visibility regarding
https://bugs.webkit.org/show_bug.cgi?id=209694.
This patch:
* Upgrades the Mac ICU headers under Source/WTF/icu from ICU 55 to ICU 62,
matching Mojave
* Introduces a minimum ICU version of 60.2 throughout the codeba
12 matches
Mail list logo