[Webkit-unassigned] [Bug 170500] [GTK] Bumping all modules of jhbuild to the latest stable version

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Apr 5 07:12:38 PDT 2017


Adrian Perez <aperez at igalia.com> changed:

           What    |Removed                     |Added
                 CC|                            |aperez at igalia.com

--- Comment #2 from Adrian Perez <aperez at igalia.com> ---
The plan looks good to me. I have added a few comments below.

(In reply to Carlos Garcia Campos from comment #1)
> Ok, this is my initial proposal:
> [...]
> libffi: 3.1 (do we really need this in the internal jhbuild? glib depends on
> 3.0 I think we can remove this one)

This can go away. Even Debian Stable has version 3.1 of libffi
nowadays: https://packages.debian.org/jessie/libffi-dev

> [...]
> librsvg: 2.36.1 -> 2.40.16

Just in case someone else wonders why not using 2.41.0: that version is
the first one including some parts rewritten in Rust. Staying in 2.40.x
saves us from building a Rust toolchain and from requiring it installed
system-wide. IMHO for now 2.40.16 is a good tradeoff between updating
and not requiring one extra complex dependency.

> [...]
> gnome-icon-theme: 3.2.1 (do we really need this)
> gnome-icon-theme-symbolic: 3.2.1 (do we really need this)
> gnome-themes-standard: 3.6.0 (do we really need this)

Using GTK+ from JHBuild does not fall-back well to using the versions
of these packages installed system-wide. I think that's the reason why
we have been keeping those in the moduleset.

> [...]
> libxml2: 2.9.1 (do we really need this)

Debian stable has this version already (exactly 2.9.1, actually). I would
remove it from the JHBuild moduleset.

> libxslt: 1.1.29 (do we really need this)

Our CMake files check for version 1.1.7, and Debian stable has 1.1.28.
Most likely we can remove it from the JHBuild.

> [...]
> orc: 0.4.17

Is there any reason to not update this? Could it be removed, even?
(Debian stable has 0.4.22, I guess we have to keep it in the JHBuild
if changing it could affect the output from tests, but that seems
unlikely. Dunno, I am not sure about this one.)

You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20170405/58816bc9/attachment-0001.html>

More information about the webkit-unassigned mailing list