Rename LightService from light-service to light_service

[adomokos]

This is the recommended naming pattern. I chose light-service based on a blog post I read at the time when I started LightService, but I think now that the name is misleading.

I am not alone with this unique naming convention. The project RestClient follows the same naming convention.

I would be curious to see what other folks are thinking about the possibility of renaming the gem from light-service to light_service.

[padi]

Also noticed this before. Never bothered opening an issue for it, but :+1:

[ramontayag]

Yes, light_service, since the project isn't Light::Service.

[variousred]

:+1:

[adomokos]

This is actually not all that easy. There is no rename in RubyGems, I have to close the current LightService repo, open up a new one with the new name and continue development on that. Which might make sense as we approach 1.0.

Does anybody else have a simpler, less invasive resolution to this?

[jeroenvisser101]

How about making a new one and publishing to both, abandoning (possibly with deprecation warnings to STDOUT) the old?

[adomokos]

That's a pretty good idea! Thank you for suggesting that.

[jeroenvisser101]

@adomokos thanks — I haven't tested that yet, but in theory, it should work.

[gee-forr]

Apologies for the bump on an ancient issue, but I would also add a spec.post_install_message to the gemspec for the deprecated version.

There are docs for post_install_message functionality.

[adomokos]

I think we know what we want to do with this. I am proposing closing it for now.