Confusion with ngMeteor?

[dandv]

https://atmospherejs.com/urigo/ngmeteor points to this repo, and so does
https://atmospherejs.com/urigo/angular

What are the high-level differences between the two?

[Urigo]

It's the same package, but I've changed the name to angular-meteor, renamed the package and the repository.
The problem is that Atmosphere doesn't support renaming packages so you have to create a new one...

[Urigo]

@dandv Do you think I should add a readme or something somewhere to help developers with that confusion?

[dandv]

Is it possible to remove the other package, so it won't clutter the search results? CC @tmeasday

The README could be just "Please see this other package", and nothing else, in the meantime.

[Urigo]

@dandv do you know how to unpublish a Meteor package?

[tmeasday]

It's not possible to unpublish packages.

Package renaming will come sometime which should solve this problem. In the meantime a README is the way to go.

[dandv]

@tmeasday: surely there must be a way to rm packages from Atmosphere at author's request?

@Urigo: see percolatestudio/atmosphere#207 and percolatestudio/atmosphere#267 ...

[udondan]

You can set it unmigrated. Then it won't be visible in meteor-search and on Atmosphere.

meteor admin set-unmigrated <package>

[tmeasday]

I guess you can do that. It's not really what unmigrated was intended for I don't suppose but it serves the purpose.