Re: [Evolution-hackers] Checking application of extensions and plugins for a software test installation

[Milan Crha <mcrha redhat com>]

On Mon, 2020-11-02 at 21:42 +0100, Markus Elfring wrote:
> > To get some background information to the archive readers (which I
> > learnt from the GNOME's GitLab ticket(s) you filled): you've been
> > building only Evolution
>
> I built a selected version of this program.

        Hi,
okay, I take it as "yes". That was probably before I pointer you to the
Building wiki page. I do not know.

> > against system evolution-data-server (eds) and you do not like
> > that Evolution installs its eds module into the directory,
> > where eds expects to have the modules installed.
>
> I suggest to recheck the functionality from the CMake scripts.
>
> elfring@Sonne:~> /usr/bin/pkgconf --variable=uimoduledir
> libedataserverui-1.2
> /usr/lib64/evolution-data-server/ui-modules

I do not see a need for it. This only supports what I wrote in my
previous mail and I wrote it because you wrote the same thing in one of
your GitLab tickets.

> This environment variable has got a known purpose.

Sure, and distributions use that as such. Successfully. It also worked
here, when I tried it. Successfully. Maybe I didn't get your claim
then.

> My approach for a test installation is clearly described, isn't it?

Well, you did not describe anything from your build process. I mean
from how exactly you are trying to build Evolution. All I wrote here
was a plain guess on some random pieces of the information I collected
from various places, some of which I noticed only accidentally.

In any case, to make life easier to the contributors, the following
wiki page had been provided years ago:
https://wiki.gnome.org/Apps/Evolution/Building
It can have its caveats, the distributions changed meanwhile, thus it
can be a "fun" to install all the dependencies, but the core parts are
working when the steps are followed precisely. I know that. I'm not
able to provide support for building such complex application as
Evolution is to every single person whom may eventually want to start
coding in such a beast, the less when it doesn't follow an article
which had been provided for that (to make life easier) very purpose.
Again, Evolution is a complex application. If the dependencies are not
complete or any other problem arises, then it's expected that the
person whom wants to contribute to such complex application is able to
solve such trivial thing as installing necessary dependencies, about
which the build process claims.

        Bye,
        Milan