Forgive me if I'm missing something but doesn't license-file provides this functionality (see https://stackoverflow.com/a/48691876) for an example.
I surmise not enough people use it although it's readily available?
Sent from my phone with my typo-happy thumbs. Please excuse my brevity
On Sat, Feb 22, 2020, 13:35 Steve Jorgensen stevej@stevej.name wrote:
Steve Jorgensen wrote:
The project I am working on now needs to include license files for all
of the 3rd party
code that it includes. Since license files are not included in
distribution packages, the
process for doing this is exceedingly complex, error prone, and in some
cases, impossible.
The build process builds URLs to license files in package source code
repositories based
on version number, but this is dependent upon several things…
The source code repository is accessible via the Internet and still
exists.
There is a tag for each version (not always true). Tags follow a consistent naming pattern with respect to version numbers
(not always
true).
I believe that it makes sense to provide a standard means for
distribution packages to
include license files and then encourage package authors to use it.
This would be similar to `{ "license" : "SEE LICENSE IN <filename>" }` in an npm package. See also https://www.npmjs.com/package/license-extractor . -- Distutils-SIG mailing list -- distutils-sig@python.org To unsubscribe send an email to distutils-sig-leave@python.org https://mail.python.org/mailman3/lists/distutils-sig.python.org/ Message archived at https://mail.python.org/archives/list/distutils-sig@python.org/message/CSS5L...