-
Notifications
You must be signed in to change notification settings - Fork 33
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 naming #3
Comments
I am aware of that, but here some (ironic) facts :
So the name conflict was really a coincidence, believe it or not :) I already used this library before i publish it as a composer package recently, that means i had But sure i noticed name conflict could be confusing for some people. Maybe we could rename this. Lets see if other people bothered by these issue, but honestly i didn't. |
Well, you can put me down for a +1 then. I use grunt.js so I'd be required to alias your tool anyway (for global usage). Not to nitpick, but to be precise, you're referencing a 0.4.0 tag, before that the tool was already widespread and used by many. |
I agree that the name could be problematic. (It's a shame that you thought of it first – I hate it when that happens!) If you're open to renaming it, perhaps "Shunt" would work? Or "SSHunt"? Both allude to the use of SSH and the idea of nudging files and commands across to a remote server. |
@toopay Grunt.js has been around since 2011, and I personally have been using it for more than a year now. A rename would be quite awesome. |
Yeah, took me a few reads to be 100% sure this wasn't Grunt.js related. |
👍 Would improve discoverability for your project as searches from Grunt always lead to the JS tool. Would prevent confusion regarding the |
@ALL Expect package re-name next week. cc @philsturgeon |
👍 |
👍 . |
Awesome — On Fri, Oct 11, 2013 at 4:23 PM, Jonathan Barronville
|
New stable release now using @philsturgeon you may need to update the grunt package info within php-loep front-page. |
@toopay updated 30dc4c428fc8bab27ef2f72291ac94ddf94ec8d5 |
@FrenkyNet thanks man. |
I can see this being a helpful tool for lots of developers, but there's also grunt.js, which is super popular and dominates the name "grunt". I don't really see why the package is not named differently. Even the gruntfile is the same name, so I doubt this is a coincidence, right?
My two cents would be to rename the package and respect the other tool's namespace, even if it is from another language.
The text was updated successfully, but these errors were encountered: