GitLab

These are long obsolete and not used.

Maybe it helps with #56

Meson 0.53 is now able to use PKG_CONFIG_PATH to sort library paths.
Therefore, the local patch included in JHBuild can be dropped.

https://github.com/mesonbuild/meson/issues/4271
https://github.com/mesonbuild/meson/pull/4325

Meson 0.53 changes the installation path of .pc files from lib/pkgconfig
to libdata/pkgconfig on FreeBSD without providing any way to override
the behavior. While it can be an improvement of usability on FreeBSD
because FreeBSD configures its pkgconf to use libdata/pkgconfig instead
of the upstream default lib/pkgconfig and share/pkgconfig, it can also
be a problem for JHBuild. JHBuild does not change the directory layout
depending on the platform, and doing so can confuse the user and make
the environment messy. Therefore, revert the change until there is a
better way to choose the default installation path.

https://github.com/mesonbuild/meson/pull/4410
https://github.com/mesonbuild/meson/pull/6343

This update drops the downstream patch used to revert the commit adding
-Wl,-rpath-link because it is now reverted by upstream.

https://github.com/mesonbuild/meson/pull/6156

Meson 0.47 changes the way to handle external dependencies on shared
libraries significantly. Instead of just putting arguments provided by
pkg-config on the linker command line, meson tries to convert -L and -l
arguments into absolute paths to .so files by itself. This should make
library handling more reliable because an absolute path is less likely
to go wrong than an ordered list of search paths. However, due to the
big change, a few regressions is still introduced, causing modules to
fail to build in a JHBuild environment from time to time.

Ideally regressions should be fixed in a few weeks and made available in
subsequent releases. Unfortunately, I can't get my patches merged
upstream in one year, and I have to remember to patch meson manually
every time JHBuild updates meson. This is annoying because there are
always modules failing to build because of these known bugs if I forget
to patch it. Therefore, I think it is time to submit these patches to
JHBuild, so it can be applied automatically.

The above patches have been added to FreeBSD ports since Meson 0.48.
The CI runner currently used to test GLib on FreeBSD also uses it.
Given that they has been used for one year without issues, it should be
safe to use them to JHBuild as well.

https://github.com/mesonbuild/meson/issues/4270
https://github.com/mesonbuild/meson/pull/4324

https://github.com/mesonbuild/meson/issues/4271
https://github.com/mesonbuild/meson/pull/4325

Meson 0.52 introduces a new library path regression. It now tries to add
-Wl,-rpath-link when pkg-config --static returns more -L arguments than
the default pkg-config call. The intention is to tell GNU ld.bfd where
it can find dependencies of shared libraries, but the implementation
does it in a wrong order and creates more undefined reference errors
than it fixes in JHBuild environments. Since JHBuild always does native
builds and LD_LIBRARY_PATH is set, -Wl,-rpath-link arguments pointing to
installation prefixes are unnecessary in JHBuild environments.
Therefore, it is safe to work around the issue by reverting the commit
introducing the feature temporarily.

https://github.com/mesonbuild/meson/pull/5647
https://github.com/mesonbuild/meson/issues/6027
https://github.com/mesonbuild/meson/pull/6031

Meson 0.52 also changes the way to handle static libraries. It is known
to break builds for dconf and gnome-builder. Unfortunately, these two
projects don't fix them in a week and we are going to update meson
without fixing them first. We backport a patch to remove duplicates from
the linker command line to resolve 'argument list too long' error when
building gnome-builder. This doesn't fix the build failure, but it
should make it easier to debug the link_whole issue.

https://github.com/mesonbuild/meson/pull/5936
https://github.com/mesonbuild/meson/pull/6030
dconf#59
gnome-builder#1057

https://bugs.webkit.org/show_bug.cgi?id=202633
https://trac.webkit.org/changeset/250899/webkit

https://bugs.webkit.org/show_bug.cgi?id=202600
https://trac.webkit.org/changeset/250747/webkit

libxslt depends on libxml2, so those should be reordered or libxslt will
use the system libxml2 which might be too old; and dbus now depends on
expat.

Pixman has a bug which renders it unbuildable with newer Clang, so
include a patch for that.

libffi has grown a configure option to do what this patch did.

autogen.sh of these two modules does not execute generated
configure script. Use custom autogen template to execute both
scripts - autogen.sh and configure.

Note that previous attempt to use patches did not work because
these modules are not built from tarballs.

Removing UDisks as system dependency because
the dependencies are able to be built in
jhbuild now.

There is no official tarball release of mozjs52 yet, so this builds from
my mirror with my set of downstream patches that are marked for backport
in Mozilla's bugtracker.

GJS will release a mozjs52 version later today.

This adds a hunk to this patch that ensures the patch has the intended
effect on macOS as well.

We compile mozjs with --enable-posix-nspr-emulation, meaning the
dependency on NSPR can be dropped. However, it's still required in the
pkg-config file, so in practice it would still be linked if present, and
error out if not present.

https://bugs.webkit.org/show_bug.cgi?id=171612

This won't stay here, it's just for people hacking on the mozjs45 branch.
It will be replaced by mozjs52, and at that point mozjs38 will be removed.

File js/src/configure was generated with a [:space:], but the
correct syntax is [[:space:]]. Since sed version 4.3, this is
considered as a syntax error.

By default mozbuild will install headers as symlinks back to the build
directory! This is no good for standalone mozjs.

We can remove mozjs31 now, nothing else is using it.

In preparation for merging GJS's mozjs38 branch to master.

This is what I've been using to build it while developing GJS.

This reverts commit eea704a3.

This patch is still used in 3.18 moduleset.

It's a sysdep now

This patch was prematurely removed in 10895240.

See https://bugzilla.gnome.org/show_bug.cgi?id=748740

Also remove webkitgtk-2.7.91-webview-webcontext-ref.patch that is no
longer needed.

Now that the weird libtool issue is fixed in git master.

Also, add it as a dependency of appstream-glib.

Also, add a patch to make it install a binary instead of a libtool
wrapper script.

Patch is to make GNOME Online Accounts not crash immediately.

And remove webkitgtk-2.7.4-gmutexlocker.patch that is no longer
needed.

WebKit defined its own GMutexLocker before we added the same to GLib,
which is causing problems.  Cherry-pick a patch from upstream in order
to work around the issue until they do the next release.

It seems libffi always uses lib64 on x86_64, but that does not play well
with the new jhbuild strategy. Add a hacky patch to avoid this.
See https://sourceware.org/ml/libffi-discuss/2014/msg00078.html

Also remove the patch for 2.5.2 that is no longer needed.

This lets us build gitg again, which was the only remaining module that
was broken in the WebKit transition.