On Wed, 2023-05-10 at 11:54 +0100, Aoife Moloney wrote:
Additionally a couple of packages (evolution-data-services and tracker-miners) are set up so they can be built with an application-specific D-Bus prefix. Evolution has:
buildopts: rpms: macros: | %_eds_dbus_services_prefix org.gnome.Evolution
This will need to be redone so that evolution-data-services doesn't need recompilation and the prefixing can be done by changing configuration files at container build time.
Hi, I cannot speak for the tracker-miners, but in case of the Evolution, it runs in its own sandbox, separated from the host system, with bundled evolution-data-server (eds) services, thus when the user installs the Flatpak version, he/she gets the expected Evolution and eds versions, independent of what the host system has installed. Advantage: the user gets all fixes, not only client-side (Evolution) fixes. It's important, from my point of view.
In many cases, this should consist of just a few minor changes to container.yaml.
Do you mean the `evolution.yaml` is gone with this change and the dependencies are taken directly from the .spec file? The eds dependency is a problem here, as you noted, not talking that not everything from the .spec file requires a rebuild for the flatpak (most dependencies are part of the runtime).
Bye, Milan