宋文武 skribis:
> Ludovic Courtès writes:
>
>> [...]
>>
>>> I'd like to try re-package qt5 with submodules, and drop QtWebEngine.
>>> As same as Debian and NixOS did.
>>
>> And Fedora. Ricardo found this insightful discussion:
>>
>> http://lists.qt-project.org/pipermail/development/2015-February
Ludovic Courtès writes:
> [...]
>
>> I'd like to try re-package qt5 with submodules, and drop QtWebEngine.
>> As same as Debian and NixOS did.
>
> And Fedora. Ricardo found this insightful discussion:
>
> http://lists.qt-project.org/pipermail/development/2015-February/019960.html
>
> +1 for re
宋文武 skribis:
> Mark H Weaver writes:
[...]
>> Better yet, we should try to get it to use our system copies of
>> libraries whenever possible.
> Yes, as I know, the remains bundled libraries are:
> pcre, need build with '--enable-pcre16'
> jasper, not packaged yet, and need various security
Mark H Weaver writes:
> Hi,
>
> Qt includes bundled copies of a *lot* of stuff. Among other things, it
> bundles Chromium, which also bundles a lot of stuff. Someone who cares
> about Qt needs to be on top of security updates for the things it
> bundles.
>
> Better yet, we should try to get it
I’m not really taking the offer ;-), but I agree that it’s crucial to
“do something about it.”
Chromium may be the most difficult of those bundled dependencies, but
there are probably others that are easier to get rid of, as a starter.
I hope we can share work with Debian and other distros that c
Hi,
Qt includes bundled copies of a *lot* of stuff. Among other things, it
bundles Chromium, which also bundles a lot of stuff. Someone who cares
about Qt needs to be on top of security updates for the things it
bundles.
Better yet, we should try to get it to use our system copies of
libraries
