TheCakeIsNaOH
commented
2 years ago Hmm, I was hoping that this feature would go live at some point.
Since the problem is that it does not follow the NuGet "spec", and that repositories do not support it (presumably in large part since it is not available in upstream NuGet), would it be worthwhile to migrate this feature to the latest upstream NuGet codebase? That way, it would be officially part of NuGet, and hopefully then repositories would more inclined to add support for it.
There is an issue open here: https://github.com/NuGet/Home/issues/10479
Is Your Feature Request Related To A Problem? Please describe.
A few years ago there was added support to the version number which allowed package revision numbers to be added when creating a new package. However this is never being used outside of a select few, and there is no support for it anywhere else other than local repositories.
Describe The Solution. Why is it needed?
The solution is to remove this feature, due to a lack of support on repositories including our own Chocolatey Community repository, and because it diverges from the NuGet spec quite heavily.
Additional Context.
This came up as a discussion we had internally, where it was decided that continuing to keep the feature available does not make any sense as it is unlikely that support for it will be made available on repository sources that Chocolatey CLI is able to use.
This additionally leads to a discussion that needs to be had regarding the immutability of the Chocolatey Community Repository. No such discussion has yet taken place.
Related Issues
N/A