Re: declaring a license
Herbert Fortes writes ("declaring a license"):
> I am doing a QA for python-irc and the tarball
> does not have a COPYING/License file. The statement
> is done in setpu.py file and PyPi only.
>  - https://packages.qa.debian.org/p/python-irc.html
>  - https://pypi.python.org/pypi/irc/
> I talked with the upstream by github 'Issues'
> about that (no COPYING/License file ) and a version
> (12.1) which had a License file declaring one
> license (LGPL) and a setpu.py file declaring the
> actual license (MIT) in the same tarball.
>  - https://github.com/jaraco/irc/issues/106
> Now I have an email that explicit declares one
> License to all project I can put the file in debian/.
> In the tarball you only see that in setup.py file.
> Is that enough ?
I think it is. I would:
* Use curl to download copies of the two github issues #99 and #106,
and put copies of the resulting html in the source package,
in debian/ somewhere.
* Write a debian/copyright file stating that the whole package is
MIT, and containing a copy of the MIT licence. I would copy
the text from https://opensource.org/licenses/MIT.
Ian Jackson <email@example.com> These opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.