[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug#62635] Ping
From: |
Liliana Marie Prikler |
Subject: |
[bug#62635] Ping |
Date: |
Tue, 16 May 2023 06:19:13 +0200 |
User-agent: |
Evolution 3.46.4 |
Am Montag, dem 15.05.2023 um 21:36 -0400 schrieb Juliana Sims:
> When I submitted the initial patch series, Geary was failing to
> launch despite building successfully and being run under a GNOME
> environment. Adding evolution-data-server to the profile solved the
> issue, and given the lack of indication in the error message that
> that would resolve the problem, I thought it would be helpful to add
> as an input.
It is true that Geary, like Evolution, needs a running Evolution Data
Server to function correctly. However, this dependency is most often
met by adding evolution-data-server to the operating-system packages,
as not doing so causes other evolution-data-server-related issues IIRC.
> While I'm here, I've noticed there are some inputs in both
> native-inputs and inputs; namely, glib, gsettings-desktop-schemas,
> and gmime. Do you happen to know if these are likely to actually be
> required in both sets of inputs? Removing glib and
> gsettings-desktop-schemas from inputs seems not to cause issues - the
> program builds and launches fine - but this may simply be because I'm
> on GNOME; because these are dependencies of dependencies and thus
> exposed in the environment of the package; or it may be that this
> would cause issues in specific functionality that isn't tested in the
> tests that are run and isn't invoked except in specific situations.
It makes a difference for cross-builds, so you would have to check
those. In my personal experience, glib:bin and gobject-introspection
often come up as native inputs in the GNOME world, whereas glib sans
bin, gsettings-desktop-schemas and gmime are mostly regular inputs.
Cheers