G'MIC 🎩🐯 (npub140g…24hf) : You're free to say whee for G'MIC three seven three in GIMP three. The illustration, see: This is #GMIC 3.7.3 and #GIMP3 3.2.0 running in Laclin [the 17th wonder of the world into which all that is fast and light is unfurled.] I did need to patch G'MIC, in my distro, to fix a FTBFS related to "gimptool" release detection.
GIMP (npub1jxd…txs3) : However, one issue that upstream isn't responsible for is unavoidable: The fact that most SCM scripts aren't expected to work in GIMP 3 for some time.
FX-Foundry seems to be one example. In fact, FX-Foundry has been partly ported to GIMP 2.8 but I gather that it hasn't made it to 2.10 yet. I see that one reviewer is holding off on an update to GIMP 3 specifically for this reason.
If it will help, I can get FX-Foundry, or most of it, to GIMP 2.10. I should have a draft set ready this Spring. The draft set will support, I think, about 85% of the scripts.
If there is an automated tool under development that will take scripts from GIMP 2.10 to 3.2 or above, this would be one way to get FX-Foundry into the new series.
FWIW: My new script set, to be named OC-Foundry, will include updated copies of other sets such as the GimpHelp set [as the latter website seems to have shut down].
To reduce confusion due to overlap with work by other developers -- and to ensure that authors receive credit -- most menu lines in OC-Foundry will indicate the original associated websites and/or authors.
βrυɲϋs (npub1kdt…ce4r) : BTW yes. G'MIC s'exécute dans GIMP, comme le montre la capture d'écran ci-jointe.
I'd like to close with a GIMP build tip:
I presently recommend that distro developers build "libmypaint" 1.6.1 exactly, then "mypaint-brushes" 1.3.0 exactly, and finally "my-paint-brushes" git-current. git commit 08da4a48a should work for the latter package. The three "*mypaint*" packages should be configured and installed using the same prefix.
The preceding steps should permit developers to build and run both GIMP 2.10.38 and 3.2.0 on the same box. Note: The two GIMP packages need to be configured and installed using *different* prefixes.
