Klemens Böswirth

If we use `gopt` via an initial `kdbGet` for the config of `kdb`, then external commands could just mount their spec as "sub-mountpoints" below the spec of `kdb`. However, this...

> The implementations of commands depend on a specific specification for options and args, I feel like allowing the changing of those might not be a good thing. That's one...

> How would using gopts help with making it work properly? There is already one reason above (externally accessible spec). Other reasons are: - IIRC `elektraGetOpts` does not consider `meta:/default`...

> The mountpoints config seems fine No they're not. That's one of the big changes in `new-backend`. The structure of `system:/elektra/mountpoints` is totally different. > and it was mounted with...

> having mountpoints created with the old kdb will make stuff crash I don't think it's written explicitly somewhere, but it's known. I guess we should have some sort of...

> But, now with cascading lookups we can't really tell if the key we get is from the command-line(so in `proc`) or comes from the default profile, which we have...

Just to be clear, the above is only my opinion and I'm open to suggestions, but it should be pretty clear to everybody that something needs to change. Also changing...

> You know that, e.g., Linux was developed by implementing what the man pages say. Yes, but that was in 1991 and man pages were probably the only public documentation...

> What is your suggestion where to put them? Right now: Leave them. Long-term: Somewhere on the website, assuming a sensible website structure. I think we can assume that people...

> I would like to have the low-hanging fruits fixed before the lecture starts, within the new-backend branch. I'm not sure there is any low-hanging fruit in terms of structure....