Skip to content
This repository has been archived by the owner on Feb 23, 2021. It is now read-only.

Redirect packages after renames #93

Closed
natemcmaster opened this issue May 10, 2016 · 1 comment
Closed

Redirect packages after renames #93

natemcmaster opened this issue May 10, 2016 · 1 comment

Comments

@natemcmaster
Copy link
Contributor

natemcmaster commented May 10, 2016

In absence of a first-class way to "rename" a package on nuget (like NuGet/Home#1590), we should find a way to help users with package renames. It's hard to follow package renames.

Example:

beta8  EntityFramework.SqlServer 
rc1    EntityFramework.MicrosoftSqlServer 
rc2    Microsoft.EntityFrameworkCore.SqlServer

One possible approach: issue an update to an old package that somehow throws a build error that alerts user of the new package name.

Two most recent examples of people confused by our package renames:
dotnet/efcore#5281
dotnet/efcore#5324

@Eilon
Copy link
Member

Eilon commented May 17, 2016

Very good idea but not planning to do this in bulk. If we see specific packages where people use the wrong name, we can reconsider this and either create redirect packages for those specific cases, or perhaps do the whole thing.

@Eilon Eilon closed this as completed May 17, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants