Klemens Böswirth

Yes, it's not well documented (since the feature is mostly used for testing/during development). It is briefly mentioned in the [docs for compiling](https://www.libelektra.org/compiling/compile). It also comes up in various other...

Yes, creating a custom resolver is also an option, but that is a much bigger task than just re-compiling Elektra.

One thing I noticed about our images is that they are **very** big. Maybe we can look into making them smaller, that should help with the disk space problems.

> Maybe we can add the docker build option `--squash` to avoid storing multiple layers of the filesystem. Wouldn't that mean different images can't share a layer and all images...

Okay, how exactly is our Fedora 36 Image over 2GB in size, when the base `fedora:36` image is

> the idea was to suggest which used Docker images (probably the least important ones) to remove or how to make them smaller. I see we have 4 different Debian...

> To also test cmake exclusion of modules. Probably we should make these images build upon each other to use less space? Building the images on top of each other...

I think that a big mistake with `infos/status` is the rating behind it. It is very much not obvious that this even exists and it makes properly choosing `infos/status` flags...

As a sidenote, if feasible, we might also want to investigate converting all the stuff at the beginning of the plugin README into something closer to standard YAML front matter....

> Do you have an example where the rating fails for you? Not right now, but I remember that for a time `hexnumber` was auto-selected for the `type` metadata instead...