[112337] trunk/dports/kde/kdevplatform

Joshua Root jmr at macports.org
Sat Oct 19 18:50:17 PDT 2013

On 2013-10-20 05:35 , Ryan Schmidt wrote:
> On Oct 19, 2013, at 02:03, nicos at macports.org wrote:
>> Revision: 112337
>>          https://trac.macports.org/changeset/112337
>> Author:   nicos at macports.org
>> Date:     2013-10-19 00:03:04 -0700 (Sat, 19 Oct 2013)
>> Log Message:
>> -----------
>> kdevplatform: update to 1.5.1, solve license conflict with openssl
>> Modified Paths:
>> --------------
>>    trunk/dports/kde/kdevplatform/Portfile
>> +#Binaries do not link to openssl, nor use the ssl backend of kdelibs4
>> +license_noconflict  openssl
> Now I'm curious to know what the difference is between "license_noconflict openssl" and "license-append OpenSSLException".

license_noconflict openssl means this port is not a derivative work of
openssl (which among other things means it doesn't link with its libs).
It actually probably shouldn't list openssl itself, but rather whatever
port pulls in the openssl dependency, because if this port ever changes
such that it links with openssl or links with something that links with
openssl etc., there will be a conflict.

license-append OpenSSLException doesn't do anything useful, because
OpenSSLException is not a license in its own right but an exception to
another license, which says you can distribute binaries linked with
openssl even if the rest of the license would normally prohibit that.

If a port's license is GPL-2+ with an openssl linking exception, you
write 'license {GPL-2+ OpenSSLException}' (note the braces --
OpenSSLException is modelled as a license that conflicts with everything
except openssl).

- Josh

More information about the macports-dev mailing list