Martchus

openqa: Clone https://openqa.opensuse.org/tests/4221654 (yet another test 2)

To support this in the GUI I'll just have add a mapping to a "known field". This is of course also beneficial to the CLI. It is just the question...

I have added this as "Synopsis" in https://github.com/Martchus/tagparser/commit/7ba8e0f9064f51eb961215a2cfa1aeaa3fc4030e because "Synopsis" is already a known field with a mapping for Matroska. So I only added mappings for MP4 and ID3v2.

Note that only a few adjustments are required to make the `libsyncthing.so` use-case *basically* work: * adjustments in Syncthing's repo itself: https://github.com/Martchus/syncthing/tree/libsyncthing * C++ interface and CMake integration for building...

Those should not be hard to find. In my tests I just added a sleep() at the end and stopped the debugger. I guess all threads it shows (beside the...

> At the very least we need to be able to not spew stuff to stdout, as stdout may not be "ours" I'd embrace that feature, too. However, I remember...

> It would be nice if we can iron out the added interface during RC. I actually see no reason to put time pressure on this. Your recent interface changes...

I based my basic C-bindings and integration into Syncthing Tray now on the latest master. It basically works and I didn't need to modify any files of Syncthing itself anymore....

Another thing: I've just tried to consume Syncthing as a Go module in order to move the additional files of my C-bindings to a different repo. That basically works but...

Checking those files in doesn't seem like a nice solution indeed. The solution proposed by @calmh seems good. I needed to add a build step for the asset generation on...