Linked by Thom Holwerda on Wed 18th Jul 2007 22:02 UTC
"Forget software politics for a minute - what does the new Samba licensing mean for the version you're actually running, and for the distribution that packages it for you? Samba maintainer Jeremy Allison explains."
Permalink for comment 256438
To read all comments associated with this story, please click here.
I read a developer 'complain' as he had a software (GPLv2 and later) combining Qt (GPLv2 only) and Samba.
He is unhappy about the change of Samba from GPLv2 to v3, as it means that he has to stop his project: Qt and Samba are no longer compatible due to Samba change of licensing..
So it's nice for Samba developers to gain compatibility with Apache code, but this change of license do create problems.
Member since:
2005-07-06
I read a developer 'complain' as he had a software (GPLv2 and later) combining Qt (GPLv2 only) and Samba.
He is unhappy about the change of Samba from GPLv2 to v3, as it means that he has to stop his project: Qt and Samba are no longer compatible due to Samba change of licensing..
So it's nice for Samba developers to gain compatibility with Apache code, but this change of license do create problems.