Please restore LICENSE file and drop the coherent.licensed dependency.

[fourtysixand2]

For the same reasons both changes were backed out for setuptools.

pypa/setuptools#5001
pypa/setuptools#5002
coherent-oss/system#22

I'm surprised the lessons learned were not followed here?

Thanks

[jaraco]

This concern is managed at the skeleton scope, so transferring there.

[jaraco]

See coherent-oss/system#24, where I've detailed the motivations and objective. I'm working on getting some authoritative advice there before I flip-flop all the projects on this concern.

[fourtysixand2]

@jaraco I'm still confused as to what goal you are trying to achieve forging ahead with a bad idea that causes nothing but annoyance and extra work for distribution and package maintainers. You are adding to the circular dependency issues and opening up a can of worms legal wise by not having the license file with the source code (see the setuptools issues above). You also seem to be neglecting the cases of someone cloning or forking your code and not including it in the tarballs.

If anything skeleton should make sure a license file exists or includes one in your other projects when created. You are attacking this from the wrong direction in my opinion.

As a lawyer friend I ran this by said, "why die on that hill over literally something that takes one second". (Adding the license file and never touching it again)

Besides setuptools which you reversed direction on, of the builds I maintain I count zipp, portend, jaraco.functools, jaraco.collections, and tempora that you've removed the LICENSE file from.

Slackware-current has held off upgrading python-zipp for the time being as well.

edit: The following projects where you have removed the license but not yet pushed new versions that I also maintain slackbuilds for: jaraco.classes backports.tarfile jaraco.text jaraco.context inflect importlib_resources importlib_metadata

[macserv]

On behalf of hundreds of thousands of engineers working at large enterprises in regulated industries, a LICENSE file is absolutely required by most open-source software procurement systems, and we are functionally blocked from consuming jaraco.functools>4.1.0.

Professionally speaking, restoring the LICENSE file would seem to be the prudent path at the present time if you would seek to avoid forking or other complications.

On a personal level, I've read through the motivations you've linked above. Your goals certainly seem worthy, and I sincerely hope you can identify a workable path toward them.

[nicorikken]

We came here because our software scanner failed to conclude the license of the Jaraco libraries, resulting in an error. A LICENSE file with the MIT license text would have satisfied the scanner, as mentioned by @macserv