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 not have installed.
> > 
> > To be honest, I don't know. Feeling?
> 
> 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') refer to the previous API
of WebKitGTK. That's no longer supported and it is not available in
buster, all packages depending on the old webkitgtk have either been
removed or they switched to webkit2gtk.

> Maybe we should only mention "webkit2gtk", which turns out after all
> to be fairly transparently connected to the name of the main library
> packages it builds (even if the -gtk2 suffix on one of them is a bit
> mystifying).

I think so, plus if you a package named *webkit2gtk* then you
directly or indirectly depend on libwebkit2gtk-4.0-37 and
libjavascriptcoregtk-4.0-18, so you are affected.

> >>         Users of a modern desktop environment with older (roughly,
> >>    pre-Pentium IV) CPUs may wish to delay upgrading until then.
> > 
> > Reading again bug 930935 it seems that there are still devices in
> > production, so age isn't a good qualifier. I put it in because it
> > seems I don't have much inspiration for this at this moment.

Maybe you can mention "embedded CPUs", which seem to be the other type
of CPUs without SSE2 (e.g. AMD Geode).

> > Close. https://tracker.debian.org/pkg/webkit2gtk shows that there
> > is also javascriptcoregtk to grep.
> 
> It looks like the only way I'd have that is if I had manually
> installed it to support some sort of local JavaScript GUI, and I'm
> hoping I would remember writing one of those.

There's also a command-line javascript interpreter (installed in the
-bin) package.

> > +  <section id="webkit2gtk-on-non-sse2" arch="i386">
> > +    <title>WebKitGTK (initially) requires SSE2 support</title>
> 
> Maybe "Webkit2gtk", or then again maybe just "WebKit".

I wouldn't say just "WebKit", there are other WebKit ports (in
particular the Qt one is in stretch and buster).

Berto

Reply via email to