Klemens Böswirth

Okay let me clarify that... Of course smaller PRs are better. The question was more, if the move to specialised hooks should be made ASAP as well (in a follow-up...

> * `kdb editor` Has various problems anyway, but yes cascading keys definitely don't make sense here. > * `kdb export` (which is actually an cascading read but it doesn't...

> Moreover, I second the questions from @kodebach. I didn't really have any questions... I made some suggestions. But I may be able to answer your questions. I don't think...

> if no namespace given, simply use the user: namespace or system: if called by root but abort in ambiguous cases I don't really like the dependency on "user is...

> For meta-set spec: might be a default worth considering. But then again we would have a "surprising" magic. The fact that `kdb meta-set` defaults to `spec:/` trips me up...

I wouldn't say it is easier in any way, but it could certainly be combined.

@markus2330 This may be an issue for FLOSS, especially if the patch provided by you actually solves everything.

I have now assigned this issue `1p`. This applies, if you just make the packages work by updating the versions. If you also fix the warnings (Note: not all of...

I don't think the current CMake setup allows a partial install (wouldn't really make sense). You could choose a reduced set of plugins when configuring CMake and then do that...

> I wonder how a PR for this issue should look like since the PKGBUILD is committed in the AUR I don't think a PR is necessary, unless you need...