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

Package redirects #2736

Closed
SimonCropp opened this issue Oct 16, 2015 · 4 comments
Closed

Package redirects #2736

SimonCropp opened this issue Oct 16, 2015 · 4 comments

Comments

@SimonCropp
Copy link
Contributor

In many cases people want to rename a package. ATM there is no easy way to do this, you basically have to release a broken version of the old package with some kind of message to move to the new package. It would be nice to have this handled in a more seamless way by nuget.

If you are willing to hack many things in the nuget toolset then you can handle it yourself, but it is painful. Here is the work we had to do to move users to a new package Particular/NServiceBus#2113

@yishaigalatzer
Copy link

That's something I've been wanting for a while for a few more scenarios.

This issue should go to the home repo, as it is not a server issue.

Worth a good discussion to cover all the scenarios (both tooling and user scenarios).

Thanks!

@SimonCropp
Copy link
Contributor Author

@yishaigalatzer is there an existing issue tracking it? or should i move this to the home repo?

@yishaigalatzer
Copy link

Move it. This is something I wanted as a nuget customer. But I don't believe it is tracked on github

@maartenba
Copy link
Contributor

This issue was moved to NuGet/Home#1590

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

3 participants