[Starlingx-discuss] MariaDB and TokuDB module License Issue
Don, I am looking at a CentOS-8 update and saw the only real change is to disable the TokuDB module. I looked up TokuDB and while it's older, it's GPLv2.0, not AGPL as suggested by the spec file. If we drop that patch and use the upstream MariaDB RPM, will that resolve license concern? I think the only patch to mariadb is to disable Toku. Sau!
Looking at the unmodified source tarball, the storage/tokudb/PerconaFT/README.md file has the following: License ------- PerconaFT is available under the GPL version 2, and AGPL version 3. See [COPYING.AGPLv3][agpllicense], [COPYING.GPLv2][gpllicense], and [PATENTS][patents]. [agpllicense]: http://github.com/Percona/PerconaFT/blob/master/COPYING.AGPLv3 [gpllicense]: http://github.com/Percona/PerconaFT/blob/master/COPYING.GPLv2 [patents]: http://github.com/Percona/PerconaFT/blob/master/PATENTS along with the storage/tokudb/PerconaFT/COPYING.AGPLv3 file. I expect this is why we had to drop tokudb from the source tarball. -----Original Message----- From: Saul Wold [mailto:sgw@linux.intel.com] Sent: Thursday, February 20, 2020 10:01 AM To: Penney, Don; starlingx-discuss@lists.starlingx.io Subject: MariaDB and TokuDB module License Issue Don, I am looking at a CentOS-8 update and saw the only real change is to disable the TokuDB module. I looked up TokuDB and while it's older, it's GPLv2.0, not AGPL as suggested by the spec file. If we drop that patch and use the upstream MariaDB RPM, will that resolve license concern? I think the only patch to mariadb is to disable Toku. Sau!
participants (2)
-
Penney, Don
-
Saul Wold