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

Consider bringing back "unlikely to service" packages so that we have a place to build them #92

Open
ericstj opened this issue Jun 27, 2024 · 2 comments

Comments

@ericstj
Copy link
Member

ericstj commented Jun 27, 2024

Here's an interesting case for maintenance-packages: dotnet/runtime#54341

Right now we don't build many of these packages any more because they no longer contain serviceable implementations - just facades / not-supported assemblies / reference assemblies. We could bring them back in maintenance-packages just to keep them building and update dependencies.

I think for this to be worthwhile we'd need to do it holistically and have enough customer value in doing so to warrant the work.

@carlossanlop
Copy link
Member

From dotnet/runtime#54341 :

  • System.Security.AccessControl

From #42 :

  • System.IO.FileSystem.AccessControl
  • System.IO.Pipes.AccessControl
  • System.Reflection.TypeExtensions

@carlossanlop
Copy link
Member

From #183

We might have to migrate System.ValueTuple after all.

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

2 participants