add license to repository

[TomasTomecek]

I'm trying to package urwidtrees to Fedora and just realized that license is not available. Would it be possible to add it? Can provide patch.

https://help.github.com/articles/open-source-licensing/

[pazz]

done. thanks for the link!

[TomasTomecek]

Sweet, thank you!

[TomasTomecek]

If you could provide a new release with the license, that would be awesome.

[pazz]

OK, but it will take a few days.

[TomasTomecek]

no worries, take your time

[pazz]

actually, there always was urwidtrees.__license__ set to GPL3...

[TomasTomecek]

But without license text it doesn't mean anything.

https://fedoraproject.org/wiki/Packaging:LicensingGuidelines?rd=Packaging/LicensingGuidelines#License_Text second paragraph

Sorry about the confusion, my point with this issue was to add license text (yes, license is set correctly to GPLv3+).

[djmattyg007]

I would like to package this for Arch Linux and would also ideally have a new tagged release. Is there anything I can do to help push this through ASAP?

[djmattyg007]

I just noticed that there's a release on PyPI for version 1.0.1.1, but there doesn't appear to be a matching tag in the git repository, and judging by the release date, my guess is it doesn't include a license file.

https://pypi.python.org/pypi/urwidtrees/1.0.1.1

[TomasTomecek]

@djmattyg007 #24 (comment)

The way I went with this in Fedora is that I used git snapshot with license and stored git commit in build id: http://koji.fedoraproject.org/koji/buildinfo?buildID=738505

[djmattyg007]

The Arch User Repository allows git packages, but I'm hoping to avoid going down that road. I'm not going to wait around forever though.

[pazz]

sorry @TomasTomecek , I meant to push this ages ago and forgot.
I cleaned up a bit and tagged/pushed version 1.0.2, which includes a LICENCE file.
I do not maintain the PIP version, and accordingly, removed the link in the README.

[djmattyg007]

Awesome! Thank you very much!