Paul Gevers wrote:
> Justin B Rye wrote:
>> + It is also intended that the buster-backports archive will receive an
>> + updated package once that archive opens up for uploads, so an
>> alternative
>> + could be to install webkit2gtk
>> + from there once it's available.
>
>
Hi Justin,
On 30-06-2019 13:17, Justin B Rye wrote:
> + It is also intended that the buster-backports archive will receive an
> + updated package once that archive opens up for uploads, so an
> alternative
> + could be to install webkit2gtk
> + from there once it's available.
Alberto Garcia wrote:
> Justin B Rye wrote:
>> The trouble with talking about WebKitGTK is that besides
>> libwebkit2gtk-* there are also a couple of packages like
>> libwebkitgtk3.0-cil that look as if they'd be relevant to this but
>> aren't.
>
> Packages named *webkitgtk* (without the '2')
On Sat, Jun 29, 2019 at 08:36:34PM +0100, Justin B Rye wrote:
> >> And how are we deciding when it's "WebKitGTK" and when it's
> >> "webkit2gtk"? Bear in mind that users have no easy way of
> >> mapping from the name of a source package to the name of the
> >> specific library they might or might
Paul Gevers wrote:
> Justin B Rye wrote:
>> And how are we deciding when it's "WebKitGTK" and when it's
>> "webkit2gtk"? Bear in mind that users have no easy way of mapping
>> from the name of a source package to the name of the specific library
>> they might or might not have installed.
>
> To
Hi Justin,
On 29-06-2019 12:24, Justin B Rye wrote:
> And how are we deciding when it's "WebKitGTK" and when it's
> "webkit2gtk"? Bear in mind that users have no easy way of mapping
> from the name of a source package to the name of the specific library
> they might or might not have installed.
On Sat, Jun 29, 2019 at 12:03:05PM +0200, Alberto Garcia wrote:
> > @Alberto, did you have any intention to upload to backports once
> > buster is released? If so, do you think it is OK to mention this
> > in the release-notes?
>
> Yes, my plan is to publish backports of every stable WebKitGTK
>
Paul Gevers wrote:
> +
> +Initially no support for WebKitGTK based applications on non-SSE2
No initial support for WebKitGTK-based applications on non-SSE2
Or maybe just
WebKitGTK (initially) requires SSE2 support
And how are we deciding when it's "WebKitGTK" and when it's
On Sat, Jun 29, 2019 at 11:18:52AM +0200, Paul Gevers wrote:
> On 27-06-2019 13:27, Paul Gevers wrote:
> > We like to support non-sse2 on i386, but we are not comfortable fixing
> > webkit2gtk at this stage of the release. Therefore, we will not unblock
> > this change, but we want the release
Hi all,
On 27-06-2019 13:27, Paul Gevers wrote:
> We like to support non-sse2 on i386, but we are not comfortable fixing
> webkit2gtk at this stage of the release. Therefore, we will not unblock
> this change, but we want the release notes to mention this, so users are
> warned.
I cooked up the
10 matches
Mail list logo
