Powershell wrapper for Nuget-License #193
Closed
zola-25
started this conversation in
Show and tell
Replies: 1 comment
-
I've learned that, in the absense of a software full licensing terms (even if it's just, for example, the standardized MIT verbatim except for the placeholders), it's not correct to render a spdx template as a license file 'on behalf' 😑 of the third party software you are using under the license. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hey, just wanted to say thanks for making this tool.
I was a bit confused to start with as it was outputting all the versions of the each package in my nuget cache, often Microsoft packages which originally came with the MS-EULA License but are now all MIT.
But just clearing my local nuget caches did the trick. Putting that in the documentation might be helpful.
I hope I've not encroached in any way, but I've created a simple powershell script that wraps some of the functionality, and appends all the singular html files into one Third-Party dependencies HTML document, making it easier just to link to that in the final application.It's probably a little overkill in some places as it pulls in the full License text for each package, so there's a lot of repetition of, for example, the full MIT License text, but it's at least fully comprehensive.Feel free to check it out here https://github.com/zola-25/CreateHtmlLicensesDocThe script mentioned fills in SPDX placeholders for Third-Party licenses which I've learned isn't the right thing to do. It will be modified or removed.
Beta Was this translation helpful? Give feedback.
All reactions