New comment by ayakael on void-packages repository

https://github.com/void-linux/void-packages/pull/32974#issuecomment-1328106649

Comment:
> > FWIW, Alpine ships both .NET 6 and .NET 7 until either are EOL for this very reason. .NET 6 being an LTS, many projects wont update till .NET 8 is out.
> 
> Yeah, I am thinking that should be the way to go. I just don't know the best approach for this. Should I just make separate packages for each version (ex: dotnet6, dotnet7, etc)? Should i just make a regular and lts packages? Thoughts?
> 
> Thanks, Ryan

We do the former (i.e. dotnet6, dotnet7). Indeed, they are times when 3 versions are supported once (like right now with .NET3.1 .NET 6 and .NET 7). As NET is designed to allow multiple versions to be installed at once, it's the right way to go. The [distribution guidelines](https://learn.microsoft.com/en-us/dotnet/core/distribution-packaging) have been especially useful to us, although rather than name ours dotnet-sdk-6.0 we went for dotnet6-sdk.