Request: allow the provided GPL plugins to build by default about little-cms HOT 2 CLOSED

I have been thinking carefully about your proposal. Unfortunately I cannot accept it. The package is distributed and advertised as MIT, so when you install by default you get binaries over MIT code. In addition, there is the possibility to install commercial plug-ins that I am also distributing under GPL3. I have other plug-ins that are not even open source, and therefore not there, but I allow GPL3 use of those two. Doing a default install of those GPL3 components would create non-MIT binaries, which could be very bad for commercial packages that only use core code. Please understand that I fully support open source, but I am an industry professional and have to favor my customers first.

My recommendation for your project is to keep a private copy of the plug-ins you use. There is a version tracking in the plug-in system, so if the system tries to use an outdated liblcms.so you will get an error.

from little-cms.

OK, understood - I had forgotten about the issue of mixing licences within a package. But I take it there's no issue requesting of the distributions that they produce separate packages for lcms2 and lcms2-plugins-gpl, so that the MIT code is all in one package and the GPL code is all in a different one (and each would have their own separate -dev packages). That should address your concerns and is a similar way that gstreamer has a number of different plugin packages). It's a bit more work for the packager to set up a packaging script but that should be a one-time job.

from little-cms.