Klemens Böswirth

This issue is still open, because it is unclear whether the current API of `elektraPluginGetPhase` is the best solution. Maybe this would be better ```c typedef enum { // ......

@markus2330 Please check whether the CM points need to adjusted, since this issue may partly be blocked by #4279.

Yes, for 1.x we want to replace all the C++ code that is currently used for mounting (in `src/lib/tools`) with C code. This will also allow us to provide proper...

For now using `kdbEnsure` is better. In the long term I don't see why we shouldn't mount `gopts` by default. But that requires changes to `kdb` (already discussed somewhere), since...

The `spec` plugin will be fixed by #3693, because it won't be a real plugin that can be mounted anymore. I'm not sure what "all plugins that were already there...

> Did you describe this somewhere? Not in detail, but in `kdb-operations.md` I wrote about explicitly calling `spec`/`gopts` and not about general global plugins. > after mounting dbus the cache...

> Other parts, however, should be new behavior for mounting: #423 (@flo91) As stated above: > Always mounting `sync` will be the responsibility of any file-based backend plugin. For the...

I have no idea what you wanted to say... But: `sync` is only needed, if the backend is file-based. It wouldn't even work, if the backend isn't file-based. That's also...

Do we really need a separate `sync` at all? The plugin literally just calls `fsync` (or the windows equivalent). A separate plugin is a lot of overhead for a single...

> Yes, as people might want to not call sync. Then make a config option. The resolver is complex enough that having config option for this makes sense. Then the...