Closed unnawut closed 5 years ago
Have you considered using the License information provided in the ./deps/<depname>/hex_metadata.config
file?
@Eptis I believe hex_metadata.config
gets its information from mix.exs
anyway?
In that case it wouldn't provide any extra advantage over the current Mix.Project.config()
?
It depends, I build my own task for this since I wasn't aware of licensir, but a lot of things currently list "Undefined" in the output of licensir, while that license information is available in the hex_metadata.config
which I used in my own task. I'm not sure if you get it through Mix.Project.config()
, would have to look into that.
I believe hex_metadata.config
also contains info for erlang packages, which I believe Mix.Project.config()
does not
@Eptis Done! Please check out the latest licensir on Hex.
v0.4.0 now relies on hex_metadata.config
which is much more complete like you mentioned.
Thanks to @pdobacz for the output dump. Some of these
Undefined
should be detectable. Also there're a lot of duplicates that can be removed.