-
-
Notifications
You must be signed in to change notification settings - Fork 10.7k
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
Adding alias diagramsnet
to cask drawio
possible?
#111512
Comments
We don't currently have a way of adding aliases to Casks, but we'd love it if someone implemented it so that we could do it just like for formulae. Perhaps you'd like to open a pull request for it? |
It looks like the application is still called Despite this, aliases / rename functionality would definitely be useful. |
Thank you for the answers. I must dig into the tap framework and understand this first. If anyone reading this thinks this is an easy fix: please go ahead. :-) |
Thnx |
I looked a bit into this. It seems like this would be a change in the brew repo and not here. There is already an alias handling in the You can see (I think) some implementation of that here: https://github.com/Homebrew/brew/blob/master/Library/Homebrew/formula.rb But there is nothing with aliases in the corresponding Maybe this should be a feature-request in the brew repo, or am I wrong here? |
Provide a detailed description of the proposed feature
Hello,
I know that homebrew-core is able to define Aliases for packages. Is the same possible for casks? I did not find anything explaining this in any docs.
I'm wondering this because today I installed the draw.io desktop version again. This was rebranded to diagrams.net some time ago.
Now, I know about the
zoom
/https://github.com/Homebrew/homebrew-cask/blob/master/Casks/zoomus.rb cask, which installs either zoom directly or as a dependency.Can we somehow adapt the Aliases functionality of homebrew-core for homebrew-cask?
What is the motivation for the feature?
Letting people install casks by historical/well-known names as well as updated, rebranded names.
Example use case
instead of
should install the same cask.
The text was updated successfully, but these errors were encountered: