-
-
Notifications
You must be signed in to change notification settings - Fork 10.8k
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
Removed version from Slack application name #6375
Conversation
As of 0.44.2, the application name still includes the version number. Is the cask outdated? (The appcast feed suggests that it is not.) |
What exactly do you mean? According git diff the version is successfully removed |
Sorry, I was unclear. The app bundle, as downloaded, is named |
Solved my error, mistake! :-) |
What is the reason that you closed this pull request without merging? |
Sorry, I thought I saw the phrase "my mistake", and thought you were withdrawing. |
I am not fond of mandating aesthetical decisions on all Cask users. However, we do not have a policy against it, and similar patches have been merged in the past. @vitorgalvao, if your opinion differs, feel free to merge. Otherwise, I suggest to close this. |
@ndr-qef I agree. If the developer includes the version number, they must have a reason. Barring cases where not renaming could break things or when the apps name is inconsistent with its own branding (and hence confusing to users), we should leave them be. That said, you’re also right in that we’ve merged similar cases in the past. I’ve done it (although I consider capitalising the first word in the name an absolutely minor change). Removing the version isn’t even a common change:
Particularly when comparing with the amount of casks we don’t remove the version number from:
Some of the renames in the first list are extremely questionable (like Music Manager) and should definitely not occur, while others (like Scala IDE) seem like they’re needed to not break things. I propose we revert most of them (including the capitalising ones I did), only leaving those that have reasons other than aesthetics to exist (this includes the previous two examples: preventing conflicts, and avoiding confusion). Some of them will be left with ugly names, but so be it, it’s the developer’s decision. Nothing is stopping users from manually renaming them, and if we ever implement alias, it’ll be even easier. @ndr-qef @rolandwalker If you agree, I’ll close this and start an issue where I’ll see if I can fit the rule somewhere, and fix the relevant casks. |
Agreed. Maybe best practice is for @cafferata, thanks for your contribution. However, it seems that maintainers want to move away from this practice. |
@rolandwalker Adding an explanatory comment sounds good. I’m already taking it into account. We’re all in agreement, so I’ll close this. Small unrelated update: Music Manager actually has a good reason to be renamed, after all. |
Thanks for the explanation(s)! |
* update URL and switch to `:latest` version scheme * more specific license * remove `:target` used to change case, per Homebrew#6375 This is a weekly build. Perhaps it belongs in the versions repo with nightlies.
Removed version from Slack application name