Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FAQ addition: upstream licensed binary #1111

Open
xenoterracide opened this issue Nov 27, 2024 · 0 comments
Open

FAQ addition: upstream licensed binary #1111

xenoterracide opened this issue Nov 27, 2024 · 0 comments

Comments

@xenoterracide
Copy link

xenoterracide commented Nov 27, 2024

Gradle (obnoxiously, maven found a better way) still wants you to commit a gradle-wrapper.jar to "your" repo, thus reuse wants you to license the file. The problem is that this file is going to fall under gradles licensing terms. Now whilst I looked those up, and added them to a .license file that doesn't really seem right. They could, for example, change the copyright holder and I would never notice. I'm updating my dependencies automatically, so that's not really a solution either, because I'm not checking.

note: not patronizingly. A jar is a binary that is a specialized zip file, and the classes inside likely have license metadata, and in fact there might be a file inside that contains the license. I haven't checked this jar.

This is on a list of files I'd rather ignore, but since no ignorelist is provided. The other being non-ai machine generated code which to my understanding can't be copyrighted; lockfiles. I'm using the suggested CC0-1.0 for those.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant