[FLOSS] kconfig plugin fails silently on meta-set

[Bujuhu]

As discussed in #4555

Steps to Reproduce the Problem

$ sudo kdb mount configrc user:/tests/kconfig kconfig
# RET: 0
$ kdb meta-set user:/tests/kconfig blue blah 
# RET: 0  
$ kdb meta-get user:/tests/kconfig blue  
Key not found
# RET: 1

Expected Result

Should either print an error on kdb meta-set user:/tests/storage/types blue blah and return a non 0 exit code or
kdb meta-get user:/tests/kconfig blue should return blah

Actual Result

$ kdb meta-set user:/tests/kconfig blue blah fails silently and kdb meta-get user:/tests/kconfig blue returns a key not found error

System Information

Operating System:
Arch Linux, Kernel 5.19.13-arch1-1

kdb and plugins version

# kdb --version
KDB_VERSION: 0.9.11
SO_VERSION: 5

Relevant Source Code

Similar to #4579 this happens because the kconfig plugin only selectively looks for the "kconfig" meta key. All others are ignored.

libelektra/src/plugins/kconfig/kconfig_serializer.cpp

Line 106 in 5702ce0

std::string metadata{ k.getMeta<std::string> (KCONFIG_METADATA_KEY) };

[Janldeboer]

I tried to reproduce the issue, but I ran into a following problem when I entered the first command.
My console shows this:

sudo kdb mount configrc user:/tests/kconfig kconfig
Password:
The command kdb mount terminated unsuccessfully with the info:
No plugin that provides kconfig could be found
Please report the issue at https://issues.libelektra.org/

Is any prior setup (e.g. installing kconfig) required?

[Bujuhu]

No, it came with the default installation for me. How did you install elektra? If you compiled it yourself, do you have log files for the compilation?

[kodebach]

The kconfig plugin is marked as "experimental"

libelektra/src/plugins/kconfig/README.md

Line 8 in cf4b6f3

- infos/status = recommended maintained compatible specific experimental unfinished nodoc concept

So AFAIK it will not (always) be packaged in the normal packages. There may be a separate -experimental package (or similar).

If you compile yourself, you need to either use cmake -DPLUGINS=ALL or explicitly include the plugin in the PLUGINS list. The default value is PLUGINS=ALL;-EXPERIMENTAL, so the kconfig plugin also wouldn't be included.

In general you also need to have the dependencies for the plugin installed before running cmake, because we automatically exclude plugins with missing dependencies. But kconfig has no dependencies so that's not an issue here.

[github-actions]

I mark this stale as it did not have any activity for one year. I'll close it in two weeks if no further activity occurs. If you want it to be alive again, ping by writing a message here or create a new issue with the remainder of this issue.
Thank you for your contributions 💖

[github-actions]

I closed this now because it has been inactive for more than one year. If I closed it by mistake, please do not hesitate to reopen it or create a new issue with the remainder of this issue.
Thank you for your contributions 💖