Hello, this is about the package server:database / xtrabackup which I would like to bring into openSUSE:Factory. https://build.opensuse.org/package/show?package=xtrabackup&project=server%3Adatabase https://build.opensuse.org/request/show/128577 The upstream code license is GPL-2.0, the upstream documentation license is CC-BY-SA-2.0. Both code and documentation are contained in the upstream source tarball from which the package is built. Currently the documentation is ignored. What should the license of the resulting source package and binary packages be? Percona has a trademark policy which is one reason why I do not create the documentation from the sources, as they contain Percona's names, logos, contact information and trademarks. http://www.percona.com/doc/percona-xtrabackup/trademark-policy.html Should generating a documentation package from these source be attempted? What would the licenses of the packages be if I add a documentation sub-package? The package also contains specific source distributions of MySQL 5.5.17 and 5.1.59. These are pristine as distributed by the MySQL project and patched during the build with patches in the xtrabackup sources. As all sources involved are GPL-2.0 I don't see a problem there, albeit the sources were obtained from a Percona server. Thanks, Andreas -- To unsubscribe, e-mail: opensuse-bar+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-bar+owner@opensuse.org
On Sat, 2012-07-21 at 17:54 +0100, Andreas Stieger wrote:
Hello,
this is about the package server:database / xtrabackup which I would like to bring into openSUSE:Factory.
https://build.opensuse.org/package/show?package=xtrabackup&project=server%3Adatabase https://build.opensuse.org/request/show/128577
The upstream code license is GPL-2.0, the upstream documentation license is CC-BY-SA-2.0. Both code and documentation are contained in the upstream source tarball from which the package is built. Currently the documentation is ignored. What should the license of the resulting source package and binary packages be?
I would assume (without having looked at the sources and based only on the above) that your spec file would state GPL-2.0 (i.e. "only" - based again only on what you have written above) and this would propogate to the binary as well. Hence, to answer your question, a simple License: GPL-2.0 in the spec file should appropriately document the licensing of the package. If at some stage you decide to package the documentation, a subpackage with license CC-BY-SA-3.0 would probably be the best way to go. If this package contains mysql sources, you'll need to check to see what happens with mysql documentation. Our mysql maintainer removes the documentation as it is under a non-free license. You might want to check with him to see exactly what is done. Finally, ensure that the GPL-2.0 text (COPYING file etc) is copied to the system in the %doc section. HTH Ciaran
Percona has a trademark policy which is one reason why I do not create the documentation from the sources, as they contain Percona's names, logos, contact information and trademarks. http://www.percona.com/doc/percona-xtrabackup/trademark-policy.html Should generating a documentation package from these source be attempted? What would the licenses of the packages be if I add a documentation sub-package?
The package also contains specific source distributions of MySQL 5.5.17 and 5.1.59. These are pristine as distributed by the MySQL project and patched during the build with patches in the xtrabackup sources. As all sources involved are GPL-2.0 I don't see a problem there, albeit the sources were obtained from a Percona server.
Thanks, Andreas
-- NOTE: I am a lawyer but I am not _your_ lawyer. This is _not_ legal advice. This is my _personal_ opinion and in no way (except by coincidence) should this be taken to represent the views of my employer. -- To unsubscribe, e-mail: opensuse-bar+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-bar+owner@opensuse.org
participants (2)
-
Andreas Stieger
-
Ciaran Farrell