Note I'm following the pkg-config version, *not* the soname.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/proje
Michael Catanzaro wrote:
> Being different than other distros is most confusing of all!
I have to disagree with that blanket assertion.
E.g., I believe it would have been much more confusing for our users if we
had shipped kdelibs 3.5.x as kdelibs4 (or "kdelibs4c2a" as Debian actually
called it
OK, thanks for the heads-up. I didn't notice this because I was looking
at the GNOME build rules, where evolution-data-server does not yet
depend on it. We'll need to coordinate with you to ensure the 2.38 ->
2.40 update goes smoothly, then. I don't expect this to be difficult:
it should be sim
Hi,
On Tue, 2022-09-20 at 08:24 -0500, Michael Catanzaro wrote:
> For now it's required by Builder and gnome-initial-setup
... and evolution-data-server, according to:
dnf repoquery --alldeps --whatrequires "webkit2gtk5.0"
and
dnf repoquery --alldeps --whatrequires "pkgconfig(we
On Tue, Sep 20 2022 at 08:24:32 AM -0500, Michael Catanzaro
wrote:
Being different than other distros is most confusing of all!
BTW part of the confusion here might be that you're used to the Fedora
package name, webkit2gtk3. But all other distros just called it
webkit2gtk. I want to avoid F
On Thu, Sep 15 2022 at 08:49:39 AM -0500, Michael Catanzaro
wrote:
I had a pet idea to change the API version to -4.5, so that we could
sync up with GTK 5 with -5.0, but this didn't seem popular upstream.
So now I'm toying with changing to -5.1 or -6.0 just to avoid
confusion caused by webkit2
Thing is, it's confusing for every distro to use different names for
the same thing, like we did for webkit2gtk-4.0. But we seem to have all
standardized on using the pkg-config version for the package name now.
Consistency with other distros is worth a lot.
On Thu, Sep 15 2022 at 03:33:12 PM
On Mon, Sep 12, 2022 at 3:53 AM Kevin Kofler via devel <
devel@lists.fedoraproject.org> wrote:
> Hi,
>
> the latest webkitgtk package now uses the following subpackage names:
> * webkit2gtk4.0 and webkit2gtk4.1 are for GTK 3,
> * webkit2gtk5.0 are for GTK 4.
>
> As you can see, the WebKitGTK sover
If you test upgrades from f36 to f37 currently, you get:
webkit2gtk4.0.x86_64 2.37.91-1.fc37 replaces webkit2gtk3.x86_64 2.36.7-1.fc36
webkit2gtk4.1.x86_64 2.37.91-1.fc37 installed as upgrade
webkit2gtk5.0.x86_64 2.37.91-1.fc37 installed as upgrade
That surely is confusing, unless you've been rea
On Mon, Sep 12 2022 at 08:34:46 AM -0500, Michael Catanzaro
wrote:
Debian hasn't packaged -5.0 yet
Actually I was only looking in unstable, but in experimental they do
have it: libwebkit2gtk-5.0-0
___
devel mailing list -- devel@lists.fedoraprojec
Michael Catanzaro wrote:
> And the Debian names are:
>
> libwebkit2gtk-4.0-37
> libwebkit2gtk-4.1-0
>
> (Debian hasn't packaged -5.0 yet, and requires the soversion appended
> to the package name.)
Debian is also notorious for having shipped kdelibs 3 as kdelibs4 and
kdelibs 4 as kdelibs5 due t
I fear there's no non-confusing way to name these packages.
The theory behind the current naming was to stick as close as possible
to the upstream pkg-config versions, which are:
webkit2gtk-4.0 (GTK 3, libsoup 2)
webkit2gtk-4.1 (GTK 3, libsoup 3)
webkitgtk-5.0 (GTK 4, libsoup 3)
(webkitgtk-5
12 matches
Mail list logo
