Klemens Böswirth

I'm not 100% sure `kdb` is the best candidate for using the high-level API. But it could be worth I try, if @hannes99 wants to invest the time. EDIT: to...

The "file" mode still make sense, if somebody doesn't want to embed the whole spec into the application because of size concerns (e.g. embedded system with separate storage for executables...

> Which advantage would the file mode of specload have compared to a normal quickdump mountpoint? That's true, without the special modification checks, the "file" mode is probably no longer...

> So it is not a type to be used for mounting the specload plugin but it is exclusively for usage with `kdbOpen(contract)`. This mode yes. But it would be...

> Using "file" to specify the file would have the advantage that the mounting code for file-based-backends would work for the specload backend. Not necessarily. This depends on what else...

Since `specload` will not support loading additional plugins, there is very little configuration possibility: 1. Some way of choosing mode between `symbol` and `executable` 2. Defining the name of the...

The tutorial for command line options already recommends `gopts` and only briefly explains how to use `elektraGetOpts`. It also explains the downsides of doing so. The doxygen comment of `elektraGetOpts`...

This list should also include the versions for the metadata keyset, e.g. `keyNextMeta` and `keyCurrentMeta`.

I suspect this is an issue with one of the `texlive` packages on Debian Sid rather than a `pdflatex` issue. The question is just which of the packages is the...

This issue blocks **all** PRs so I would say it is actually urgent. But yes it's nice for FLOSS so let's leave it. Maybe we should disable PDF generation for...