afre_orien : I’ll check. Apparently, the command is indeed compiled in the update280.gmic file, but was not send to the server, which I don’t understand.
Basically, the file
update280.gmic is a concatenation of the
stdlib file and the
gmic-community files. Theoretically, I’m not allowed to generate
update280.gmic if all licenses of the
gmic-community files are not compatible together.
From what I understand, I think we can currently choose a copyleft license (with a contamination clause, like CeCILL v.2) for applying to the
update280.gmic file, and it will be OK.
If a contributor’s file in
gmic-community has a more permissive license (e.g. LGPL or CeCILL-C), then I’m still authorized to generate the update file, and license it with a less permissive license, and people interested by a filter code in those files can still get it with the more permissive license as well.
Anyway, in the future, we have to take care of the license compatibility when a new file is added to
About filter updates:
IMHO, there are no simple answers to this problem. We have two possible approaches:
- Either we force ourselves to keep a strong backward compatibility of the G’MIC syntax and API when new versions are out, so at least, people of older versions can still update and use some of the new filters (those that do not require the use of new introduced features).
- Or, we have some breakpoints sometimes, and freeze the filter updates for a set of older versions.
I am more in favour of the second solution. As the G’MIC-Qt plug-in knows its version number, it can still get the latest filter updates that have been done for this particular version.
So, users of older versions can still use some of the filters from
And, from a developer viewpoint, having all filters use a common syntax makes things really easier to maintain (actually, I would be already dead if I had to maintain the filter codes for each possible released G’MIC versions…).
Another point to consider : The GIMP team is working on a resource manager directly integrated into GIMP. This means that in the future, plug-ins would be updated automatically for the users (just as it does on Linux, if you install it via the packages).
This will solve the problem of the updates of the plug-in binary.