Correct packages with misleading and confusing package ID suffixes about chocolatey-packages

[ferventcoder]

Agreed. At one point I held off as I thought we would just create the idea of aliases. I think deprecating them and moving forward on .portable is fine.

[TomOne]

Any plans to do this soon? This might be not on top of your priority list, but it does require only very little time.

[ferventcoder]

I wonder if adding aliases removes this work completely?

On Saturday, December 13, 2014, TomOne [email protected] wrote:

Any plans to do this soon? This might be not on top of your priority list,
but it does require only very little time.

—
Reply to this email directly or view it on GitHub
#27 (comment)
.

Rob
"Be passionate in all you do"

http://devlicio.us/blogs/rob_reynolds
http://ferventcoder.com
http://twitter.com/ferventcoder

[ferventcoder]

Ha, looking here again. Seeing my old comments.

[TomOne]

Sure. Do you have an ETA for that?

[TomOne]

I wonder if adding aliases removes this work completely?

Nope, it does not. You still need to update the packages with the correct IDs.

[TomOne]

And in addition to aliases, it would also require the ability to change the IDs of existing packages.

[ferventcoder]

Not trying be wishy washy here, even if it appears so.

I think we can both agree that changing the name needs a better story. The process now means someone with a well established package is asked to give up the download number and move forward with a new package name that doesn't have the history, stats, and download numbers. Being able to deprecate one for another to meet guidelines should not remove any benefits for the user.

We can both agree that these need better names, I'm dragging my feet a bit because I wonder if we can achieve the best thing possible, which could ultimately make the story easier for others.

[ferventcoder]

And in addition to aliases, it would also require the ability to change the IDs of existing packages.

Aliases is the ability to change the ID. It may help to draw out requirements so that the idea is easier to understand.

1. Add zero or more aliases to a package Id.
2. Aliases behave as package ids, they are not a different concept.
3. Set a primary alias (what shows on the package page).
4. Deprecate a package alias.

[ferventcoder]

This will eventually get picked back up in the core team repo.