Jehan

By the way, even if the engine is made more "tolerant" to unknown fields, it could be wise to make use of the "version" field in the brush format, no?...

Well if the fallbacks for these new features are considered acceptable (i.e. if you think the brushes are still usable even without these features), then I guess it's ok.

Well then I guess you should just version the data directory: share/mypaint/ for libmypaint vs share/mypaint-2/ for libmypaint-2. That's what we do for GIMP and that looks like it's the...

> What about git release tags? Or is it bad to rely on git for this kind of thing? Not sure what you mean. Installing automatically the data in a...

For the record, and as mentionned at: https://github.com/mypaint/mypaint/pull/538#issuecomment-354579195 I am going forward with the mypaint-brushes packaging and this contains brush versionning: https://github.com/Jehan/mypaint-brushes/releases GIMP is going to depend on this new...

Thanks @jplloyd. On our side, I am noting that we should update to the new API. Any pointer which specific API you are talking about?

How is CMake easier to work with on Windows? (real question, no trick, I just really want to understand what you mean because I never had any problems with autotools...

I am not a Windows user as well, though I regularly cross-build libmypaint for Windows, especially since we use libmypaint in GIMP. I timed it just now, just for the...

Anyway I leave open for the maintainer to see. I am not saying I am against in absolute. I only give my opinion on the topic (and also I say...

We have someone at GIMP team (with full trust on code quality) who wants to port libmypaint build system to meson. I'm going to assume that the discussion here implies...