Chris Miller
2010-Apr-01 19:18 UTC
[asterisk-users] asterisk-gplonly dependency in asterisk-addons RPM
It seems that asterisk-addons and one or more of Digium's licensed modules such as res_fax_digium have a conflict that doesn't seem to be documented anywhere I can find. In a nutshell, asterisk14-addons-core has a fake provide for asterisk-gplonly : # # core subpackage # %package core Summary: Asterisk-addons core package. Group: Utilities/System Provides: asterisk-gplonly Provides: asterisk-addons-core Obsoletes: asterisk-addons-core Requires: asterisk14-core The Digium licensed packages look for this package and prevent installation : ---> Package asterisk14-res_fax.i386 1:1.4_1.0.14-1_centos5 set to be updated ---> Package asterisk14-res_fax_digium.i386 1:1.4_1.0.11-1_centos5 set to be updated --> Processing Conflict: asterisk14-res_fax conflicts asterisk-gplonly --> Processing Conflict: asterisk14-res_fax_digium conflicts asterisk-gplonly --> Finished Dependency Resolution 1:asterisk14-res_fax_digium-1.4_1.0.11-1_centos5.i386 from digium-current has depsolving problems --> asterisk14-res_fax_digium conflicts with asterisk14-addons-core 1:asterisk14-res_fax-1.4_1.0.14-1_centos5.i386 from digium-current has depsolving problems --> asterisk14-res_fax conflicts with asterisk14-addons-core Error: asterisk14-res_fax conflicts with asterisk14-addons-core Error: asterisk14-res_fax_digium conflicts with asterisk14-addons-core A comment in the spec file would have been nice... Does anyone know if this a real technical issue, or simply a licensing conflict between GPL and Digium? Chris
Kevin P. Fleming
2010-Apr-01 20:52 UTC
[asterisk-users] asterisk-gplonly dependency in asterisk-addons RPM
Chris Miller wrote:> A comment in the spec file would have been nice... Does anyone know > if this a real technical issue, or simply a licensing conflict > between GPL and Digium?It is not a technical issue; it is an issue because some of the modules in -addons have licenses that are pure GPLv2 only, and in addition the license for MySQL-based components restricts their usage to *only* GPLv2-licensed applications unless a commercial license for MySQL is obtained. Since loading one of Digium's binary modules into an Asterisk process changes it to no longer be pure GPLv2, such usage restrictions should be taken into account. The purpose of that conflict is to ensure that the person installing the packages is made aware of the issue and that they must take explicit action to override it (thus ensuring that we don't facilitate accidental violation of third-party license agreements). If you can suggest a method to provide this information to people in some automatic way when they are made aware of the conflict by RPM, feel free to do so and we'll try to get it incorporated into the RPMs themselves. -- Kevin P. Fleming Digium, Inc. | Director of Software Technologies 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA skype: kpfleming | jabber: kfleming at digium.com Check us out at www.digium.com & www.asterisk.org