Allow users to determine package resolution strategy during package restore - direct or transitive
I am not going to debate if highest or lowest should be the default: leave the actual behavior up to the consumer. Why on earth should Microsoft FORCE users to adopt the "safest is best" strategy in the first place? Is there any reason why we cannot add a switch to nuget.exe and NPM that allows the user to decide their own package restore strategy? This way consumers of nuget can align nuget behavior to their own business strategies, be they conservative or aggressive. What I don't understand is why Microsoft has to decide this for consumers in the first place. To me this is a straight up consumer decision based on private business strategy and policy. It makes absolutely no sense why a tool vendor should allow themselves to unilaterally decide business strategy for all nuget consumers on the planet without an option to override that. It's been two years and there's no apparent movement on this issue. Leave lowest version as the default strategy if you want Microsoft, but for goodness sakes offer a switch to allow consumers to make their own business decisions.
Posted by Wil73 on Jul 8, 2017, 3:14 PM
Tags
Related issues
- struct's lifetime requirements can be bypassed via covariant field assignment
- Proposal to Reorganize the Moderation Team and Review Moderation Policies
- Progressive FPS degradation appears to be related to dota2.com — blocking the domain prevents the performance loss
- proposal: container/...: generic collection types
- Better Custom Endpoint BYOK
- A concrete policy for backward compatibility until Godot 5.0
Raise real-world problems, find people facing the same issue, and discuss solutions.4,500 issues0 comments
github (Other)
struct's lifetime requirements can be bypassed via covariant field assignment
Proposal to Reorganize the Moderation Team and Review Moderation Policies
Progressive FPS degradation appears to be related to dota2.com — blocking the domain prevents the performance loss
proposal: container/...: generic collection types
Better Custom Endpoint BYOK
A concrete policy for backward compatibility until Godot 5.0
New MTP models not supported
Tracking: 429 / Capacity Issues
Allow users to determine package resolution strategy during package restore - direct or transitive
I am not going to debate if highest or lowest should be the default: leave the actual behavior up to the consumer. Why on earth should Microsoft FORCE users to adopt the "safest is best" strategy in the first place? Is there any reason why we cannot add a switch to nuget.exe and NPM that allows the user to decide their own package restore strategy? This way consumers of nuget can align nuget behavior to their own business strategies, be they conservative or aggressive. What I don't understand is why Microsoft has to decide this for consumers in the first place. To me this is a straight up consumer decision based on private business strategy and policy. It makes absolutely no sense why a tool vendor should allow themselves to unilaterally decide business strategy for all nuget consumers on the planet without an option to override that. It's been two years and there's no apparent movement on this issue. Leave lowest version as the default strategy if you want Microsoft, but for goodness sakes offer a switch to allow consumers to make their own business decisions.
Comments (0)
No comments yet. Start the discussion.