No license file

[eoger]

Would it be possible to add a LICENSE file to this repo?

[bollwyvl]

This is presently blocking some work downstream: conda-forge/texlab-feedstock#10

Happy to PR something, if @Vurich would like to propose the copyright string...

[eira-fransham]

The license is specified in the Cargo.toml as MIT, although most of the code I write nowadays is under the Unlicense so if you need it to be relicensed I can do that. Is the file necessary if the license is specified as metadata?

[bollwyvl]

Thanks for the super quick response! A number of "distro"-style package managers don't really care much if the wording of license XYZ doesn't require distributing the _text_ of the license... But packagers still have to "tick the box" when code gets vendored/linked. It would super help if cargo "enforced" this, but can't fix that now! For texlab, which recently adopted crunchy, that's 100 or so crates, and I'm down to just this package and one other. So: no relicensing needed, just a clarification, in the repo, of the rights a user (or in my case, redistributor!) has (or had, whenever the last version went out).

[eira-fransham]

Ok sure, I’ll do that. I actually didn’t mean to close this issue, I’ll reopen it until I get around to adding the license file (which will just be whenever I’m next at my laptop).

[decathorpe]

I'm packaging this crate for Fedora Linux and came across this issue, it would be great if it could be resolved. The MIT license requires redistributed sources to include the original license text, so technically both crates distributed via crates.io and our RPM packages currently are not in compliance with your chosen license :(

Side note: From a Linux distribution point of view, even if you relicense this crate as Unlicense, having an actual license text included would still be better than not including the license text at all.

[eira-fransham]

Does this solve the issue? #7

[decathorpe]

Thanks, that solves the most important part for me - the only thing that's technically still missing is publishing a new version of this crate to crates.io so the change actually propagates to users of the crate. I can work around that for my use case, but other people my not be able to do that and would rely on a new version to be published.