Klemens Böswirth

> We need to investigate why this takes so long This is a result of #2595. Now we finally test all storage plugins. Maybe `fsync` is the root cause of...

> This is on purpose to test such KeySets. What exactly is the difference between testing a `KeySet` with just a single Key `a` then with Key `b`, etc. compared...

> The difference is for storage plugin developers: you get a very small example of when your plugin fails and not a huge test case where you need to find...

There is already some documentation. See https://github.com/ElektraInitiative/libelektra/pull/3651#issuecomment-781539532 I already added some information about the caching of the global Keyset. What else should we document and where?

## Current configuration - Cirrus CI jobs use the default `CMAKE_INSTALL_PREFIX=/usr/local` - Travis CI Linux jobs use a local folder inside the build directory - Travis CI macOS jobs use...

I am pretty sure there is a way. I just didn't look into it further yet, because it takes quite some time to test the changes on all supported systems....

I think the `RPATH` discussion plays a role in @robaerd's efforts to create better packages. I also think we should have at least one build job that tries to install...

@markus2330 Ignoring all the `RPATH` discussion, do we now have a build job that installs into `/usr`?

If the packages are installed and then tests are run, that would probably be good enough too.

jenkins build libelektra please