GitLab

!142

Fedora's exiv2 package also enables native language support, and
there's no reason not to.

!141

Use Kalev Lember's updated pkgconfig patch from Fedora.

!140

!139

#116

Even though libgdata doesn't require liboauth by default, it's better
to explicitly specify it. It protects the build against any changes in
the SDK or the libgdata defaults.

#116
libgdata#1

The library has changed the API version to 0.3.x for experiments.
A lot of changes which may break the API/ABI would come.
So, still highly recommend to use the 0.2 API version branch.

Since GLib 2.60.x, GSettings' keyfile backend is capable enough to be
the default backend for Flatpak applications. If a Flatpak doesn't
have the necessary permissions to access dconf, GSettings will
automatically switch to using the keyfile backend.

This is good because dconf isn't suited for sandboxing. It uses a
single database shared across all applications - they are free to read
and write anything, and settings are left behind even after an
application has been uninstalled. This leaves plenty of room for
mischief and accidents. In comparison, the keyfile backend uses a
separate isolated file for each Flatpak that's removed when the
application is uninstalled.

!122

Intltool was removed from version 3.34 of the GNOME SDK, but it's
still used by tracker-miners. Therefore it has to be bundled with the
build.

Tracker's master branches are now being used to develop version 3.0,
and it's not ready for use [1]. Hence the build has to be switched to
use the respective 2.3 branches.

Some changes by Debarshi Ray.

[1] https://discourse.gnome.org/t/tracker-has-branched-for-3-0-use-the-2-3-branch-if-you-want-stability/1889

!118
!125

The grilo-plugins build has started to fallback to downloading grilo
as a subproject if certain dependencies aren't met [1]. In this case,
the grilo-pls-0.3 dependency is missing because it's disabled in the
grilo build via the -Denable-grl-pls=false option.

This is a problem because network access is not available in the build
sandbox.

[1] grilo-plugins commit 34d3c5844864f0d0
    grilo-plugins!68

!124

!112

The exiv2-0.27.1-Source.tar.gz file doesn't exist at it's earlier
location. Instead, http://exiv2.org/download.html links to the 0.27.2
release.

!110

!109

!111

#128

Fallout from 70bc4806

!105

The exiv2-0.27.0-Source.tar.gz file doesn't exist at it's earlier
location. Instead, http://exiv2.org/download.html links to the 0.27.1
release.

!103

Currently the build detects the presence of the necessary dependencies
and automatically enables or disables the corresponding options. Unless
someone is keeping a close eye on the build logs, a change in the
manifest or the SDK might silently and unexpectedly change the build
options.

Ideally, the build would fail if a requested option can't be met, to
draw attention to this unforeseen change.

Unfortunately, the LibRaw build uses AC_MSG_WARN even for explicitly
enabled build options. This means that a missing dependency won't fail
the build even if the option was explicitly requested. While this is
not ideal, at least listing the options makes it clear what the
required outcome is. That way someone can manually check the logs from
time to time and see if it's living up to the requirements.

The set of build flags have been chosen to match the current reality of
automatically selected options. Hence, there shouldn't be any
user-visible change.

!91

The LibRaw-0.19.2 tarball got modified in-place to include a configure
script: https://github.com/LibRaw/LibRaw/issues/197

!90

Even though it uses Autotools, the tarball neither has an autogen.sh
nor a configure script.

!89

Fallout from 30a5e90a

!88

!87

The exiv2-0.26-trunk.tar.gz file doesn't exist at it's earlier
location. Instead, http://exiv2.org/download.html links to the 0.27.0
release.

Based on Darktable's Flathub manifest:
https://github.com/flathub/org.darktable.Darktable

!86

This should have been included in commit eac6711f, which
introduced the build and code changes to show the latest commit in the
version for non-release builds.

Original patch from Michael Catanzaro for epiphany.

!82

!81

None of the installed tests from the other modules (eg., gnome-photos
itself) are part of the Flatpak bundle. It's also questionable how much
value they would add to the Flatpak. The average non-technical user
wouldn't know about them, but a contributor might find them useful.

We already disable the extractor anyway, but Tracker still tries to
build parts of it and that fails on a missing libcue.

This commit disables that part as well explicitly.

!66

... instead of using the configure and Makefile adapter. The adapter
inverts the Meson build's enable-gtk-doc option to default to false, so
that needs to be handled.

!66

The Autotools build didn't use --disable-dogtail, even though the SDK
doesn't have Dogtail. It only worked because configure.ac doesn't
actually check for the presence of Dogtail. The Meson build doesn't
check for it either, but merely to imitate the Autotools build.

It's better to spell out exactly what's going on.

There has never ever been a --disable-documentation build flag, yet,
somehow it has been present in the Flatpak manifest since it was first
added to the gnome-apps-nightly repository.

GNOME Online Accounts has a --disable-documentation flag to disable
generating the man page for goa-daemon(8), which is already covered by
the --disable-backend flag. So, it might have been a typo while writing
the manifest.

Currently available versions of liboauth, such as 1.0.3, don't build
against OpenSSL 1.1.0, and that has been failing the nightly builds.
It does work with NSS, though; and, for what it's worth, Fedora builds
liboauth against NSS too.

https://github.com/x42/liboauth/issues/9

grilo-plugins#13

Some of the build options don't fully work as advertised.

tracker-miners#27
tracker-miners#29

The tracker-miners module is only needed for:
  * the org.freedesktop.Tracker1.Miner.Files.service file and symlink
    that are used by tracker_miner_manager_get_status
  * the org.freedesktop.Tracker.Miner.Files schema that's used to get
    any custom locations configured through Settings -> Search

The only ELF binaries are in /lib/tracker-miners-2.0. Since those are
not global, and there are simply no other binaries, it ought to be
safe to remove them.

It never put anything in /bin.

Fallout from 66c4e62b

... otherwise it will still attempt to build with Autotools.

This should have been included in commit  0801c9e9, which
switched tracker to Meson.

Strictly speaking, the entire /share/dbus-1 tree should be removed,
and not just /share/dbus-1/services. This doesn't matter in practice
because other modules do put things in /share/dbus-1 that are needed in
the Flatpak bundle, so there's no empty /app/share/dbus-1 lurking
around.

The --disable-introspection build option was lost, but an option to
disable the systemd units was gained.

tracker#37

Fallout from 0cadae91