-
Notifications
You must be signed in to change notification settings - Fork 62
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
Add NUnit template packages to text-only packages #167
Conversation
Hmm. I'm not a fan of adding vs. the alternatives. Note that it's not a .NET Foundation/Microsoft package. (For future reference, these templates came into the product via nunit/dotnet-new-nunit#13.) Alternatives:
I know I've poked a lot of times about why we got rid of the text-only package decomposition-recomposition, but this is an example of where that automation shines. It lets us keep redisting this text-only stuff without worrying about maintaining it so intentionally and bloating this repo even further. |
What we got rid of was the reference-only package IL decomposition/recomposition. Text-only packages was a bit of a side effect of that. But, we could add back just the text-only package part of it. My main concern with that is that our long term goal is to be able to generate a tarball without doing a production build and that would move away from that goal. I would rather have us add the repo. |
Something I think is interesting here is that arcade-powered source-build is caching the production build: we could do text-only prebuilt decomposition during the official build and include the text-only layout in the intermediate nupkgs. If we still have to download some previously-source-built bits to make the tarball buildable, downloading intermediate nupkgs isn't much different. But actually beyond that, we could do text-only prebuilt decomposition (even ref-only decomposition) without a production build at all. dotnet/source-build#831 lays out a way to do that. On the other hand, the less infra, the better, and if we can just keep adding repos, that sounds best. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it might be fine to accept this for now, I realized https://github.com/nunit/dotnet-new-nunit doesn't have a lot of changes over time so I wouldn't expect this particular text-only package to be a problem.
I logged dotnet/source-build#1786 to look into adding the repo and noted that we should remove these if we do. Sound okay for now? |
Sounds good to me, thanks for filing. 👍 |
* Add NUnit templates as text-only packages.
No description provided.