Klemens Böswirth

I don't understand why this unimportant... What I understood is: You suggest that we should publish a new version of Elektra every time a dependency gets updated. That seems crazy...

There are some commits in this PR that shouldn't be here... As for the `hexnumber` bug: I'm not sure why it doesn't fail on `kdb meta-set`, but AFAIK `hexnumber` doesn't...

I'm pretty sure this is all still #2723. The `default:/` namespace now exists, but on `master` backends for `default:/` (including when implied by a cascading backend, e.g. via `spec-mount`) don't...

How would fixing the `origvalue` issue help within anything here?

1. `origvalue` was a bad design. 2. No `type` cannot take the responsibility for all transformations, unless there are "sub-plugins" which are called by `type`. (see #3626) It is not...

This PR wasn't marked as "CM", so I missed it. Otherwise I would have told you this sooner... Please rebase and adapt your code. The `next()` function was recently removed....

Also please add a test case somewhere that shows the new code works as intended.

> Right now there are no tests for this feature as fare as i know. The easiest place to add some would probably be `testscr_check_basic`, i.e. in [tests/shell/check_basic](https://github.com/ElektraInitiative/libelektra/blob/master/tests/shell/check_basic.sh).

I checked the source code and it's not as simple as switching `keyName` to `keyUnescapedName`, but is pretty simple to make the hashmap work with zero-bytes. (details in the top...

If we release like this, the files should also be added to `.gitignore` until there is a proper fix. Then you at least don't have to be careful to not...