Hi,
I'm writing a compiler that will eventually be a build dependency of glibc and so (hopefully!) end up in Fedora. I want to use two Python libraries as dependencies, but I'd like clarification that both have ok licenses for Fedora before I dive in.
1. https://pypi.python.org/pypi/arpy
This one has no LICENSE file; the top of the source file says this:
# Copyright 2011 Stanisław Pitucha. All rights reserved. # Copyright 2013 Helmut Grohne. All rights reserved. # # Redistribution and use in source and binary forms, with or without modification, are # permitted provided that the following conditions are met: # # 1. Redistributions of source code must retain the above copyright notice, this list of # conditions and the following disclaimer. # # 2. Redistributions in binary form must reproduce the above copyright notice, this list # of conditions and the following disclaimer in the documentation and/or other materials # provided with the distribution. # # THIS SOFTWARE IS PROVIDED BY Stanisław Pitucha ``AS IS'' AND ANY EXPRESS OR IMPLIED # WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND # FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL Stanisław Pitucha OR # CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR # CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR # SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON # ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING # NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. # # The views and conclusions contained in the software and documentation are those of the # authors and should not be interpreted as representing official policies, either expressed # or implied, of Stanisław Pitucha.
Could you confirm that this is 2 clause BSD ("License: BSD") and that I just need to get the maintainers to add a LICENSE file for this to be ok for Fedora?
2. https://pypi.python.org/pypi/pyelftools
This one has two license files, LICENSE:
pyelftools is in the public domain (see below if you need more details).
pyelftools uses the construct library for structured parsing of a binary stream. construct is packaged in pyelftools/construct - see its LICENSE file for the license.
-------------------------------------------------------------------------------
This is free and unencumbered software released into the public domain.
Anyone is free to copy, modify, publish, use, compile, sell, or distribute this software, either in source code form or as a compiled binary, for any purpose, commercial or non-commercial, and by any means.
In jurisdictions that recognize copyright laws, the author or authors of this software dedicate any and all copyright interest in the software to the public domain. We make this dedication for the benefit of the public at large and to the detriment of our heirs and successors. We intend this dedication to be an overt act of relinquishment in perpetuity of all present and future rights to this software under copyright law.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
For more information, please refer to http://unlicense.org/
and elftools/construct/LICENSE:
Copyright (C) 2009 Tomer Filiba, 2010-2011 Corbin Simpson
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Am I right that the second is MIT (Modern Style with sublicense) and that this package would have "License: Public Domain and MIT"?
Thanks in advance, Gary
On 07/28/2016 06:20 AM, Gary Benson wrote:
Could you confirm that this is 2 clause BSD ("License: BSD") and that I just need to get the maintainers to add a LICENSE file for this to be ok for Fedora?
This is correct. Adding the LICENSE file is a nice to have, but not a blocker, because the .py file includes the license text and the binary package will include the .py file (presumably).
Am I right that the second is MIT (Modern Style with sublicense) and that this package would have "License: Public Domain and MIT"?
Yes.
Thanks for checking,
~tom
== Red Hat
Tom Callaway wrote:
On 07/28/2016 06:20 AM, Gary Benson wrote:
Could you confirm that this is 2 clause BSD ("License: BSD") and that I just need to get the maintainers to add a LICENSE file for this to be ok for Fedora?
This is correct. Adding the LICENSE file is a nice to have, but not a blocker, because the .py file includes the license text and the binary package will include the .py file (presumably).
Am I right that the second is MIT (Modern Style with sublicense) and that this package would have "License: Public Domain and MIT"?
Yes.
Thanks for checking,
Awesome, thanks Tom.
Cheers, Gary