Closed jonpryor closed 2 years ago
Thanks for the clean PR. Unfortunately I have moved on from .Net and can no longer build/release this project (not even sure the release script still works).
LMK if you feel like releasing a patch (don't know how much you need it), and I can DM you a temporary API key for it.
Hi @gluck thank you so much for everything you've done for .NET. This project is amazing and is still being super useful for the whole ecosystem.
Would you be interested in adding me as an owner to this project so I could continue maintaining it, merging PRs, making releases? Ideally also I'd need to be an owner on https://www.nuget.org/packages/ILRepack to be able to publish new versions.
If not, no problem, my current plan is to merge PRs into my fork and publish a NuGet with a different ID.
Thanks again!
Hi @KirillOsenkov ,
happy to do so, I've moved on from .Net, doesn't mean everybody should ! I've invited you to the GitHub repo, will do on nuget next.
@timotei is that alright with you being both collaborators on this repo ?
@gluck Sure 👍 I wasn't able to be properly involved in the past year(s) :(, so having another collaborator is great
Welcome @KirillOsenkov 👋
Amazing! my nuget.org account is https://www.nuget.org/profiles/kirillosenkov
Context: https://docs.microsoft.com/en-us/nuget/reference/nuspec#license Context: https://docs.microsoft.com/en-us/dotnet/standard/library-guidance/nuget#important-nuget-package-metadata Context: https://docs.clearlydefined.io/curation-guidelines
Certain internal Microsoft tools check NuGet license information by using ClearlyDefined curated data to determine verified license information for packages which don't "clearly define" their license.
The
ILRepack
andILRepack.Lib
NuGet packages do no specify any license information within their.nuspec
files.Update element:
build.groovy
so that the generated.nuspec
files contain the `The value of the
<license/>
element must be an SPDX license identifier.This is slightly complicated by the fact that I can't find an easy way to get
com.ullink.nuget
to emit XML attributes. Fortunately, if it processes a closure, we can get access to the underlyingMarkupBuilder
instance, which allows us to create an XML element that contains both attributes and content.