Congratulating @marcodejongh on swiftly unmigrating package

[dandv]

marcodejongh/meteor-packages-lightning#1

👍

[marcodejongh]

@dandv no problem, didn't know about the set-unmigrated command.
Probably would be better if the command is changed to hide-package.

[dandv]

We actually sorely lack any commands to hide, remove or rename packaging. CC @ekatek, @tmeasday.

[mizzao]

Being able to rename packages would make it far easier to migrate to "official" versions as well.

[dandv]

Indeed, any news, @estark37?

[estark37]

Sorry, I don't have anything to report! I'm not working on the package system right now.

[mizzao]

@dandv I think you meant @ekatek.

@ekatek: we are asking about whether it would be possible to rename packages and "move" them between organizations to facilitate migrations instead of asking everyone to change the package names referenced from apps and other packages. It seems the easiest way to implement this would just be to have the old name be an alias for the new name, with continuous versioning.

[tmeasday]

@ekatek - Alternatively, is the unofficial advice that that feature isn't coming soon and we should just cut our losses and start renaming packages the "ugly" way? (i.e. making a new package, marking the old package unmigrated, hoping users figure it out eventually/writing stuff in the old README).

Totally appreciate that you guys are working on other stuff and renaming isn't a priority. But if you have any hints you can give us it might help people making these kind of decisions.

[ekatek]

That feature will come one day, but I am not sure when. We will try to have
a better answer for this in January -- many people are out of office for
the holidays right now, so figuring this sort of stuff out is difficult.

On Tue, Dec 23, 2014 at 3:15 PM, Tom Coleman [email protected]
wrote:

@ekatek https://github.com/ekatek - Alternatively, is the unofficial
advice that that feature isn't coming soon and we should just cut our
losses and start renaming packages the "ugly" way? (i.e. making a new
package, marking the old package unmigrated, hoping users figure it out
eventually/writing stuff in the old README).

Totally appreciate that you guys are working on other stuff and renaming
isn't a priority. But if you have any hints you can give us it might help
people making these kind of decisions.

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

[marcodejongh]

@ekatek Any updates?

[ekatek]

CC @debergalis

[debergalis]

Not a priority right now.