Skip to content
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

Eclipse casks overwrite each other's symlinks. #8841

Closed
leojweda opened this issue Jan 12, 2015 · 6 comments
Closed

Eclipse casks overwrite each other's symlinks. #8841

leojweda opened this issue Jan 12, 2015 · 6 comments

Comments

@leojweda
Copy link

Since all Eclipse installations have the exact same name "eclipse.app", when a second eclipse cask is installed it overwrites the previous symlink.

@vitorgalvao
Copy link
Member

We’re aware of it, but that’s an upstream problem, really. Why do they all have the same name to begin with? What do people usually do with them?

We can’t simply start renaming them, as that can break expectations to users.

@leojweda
Copy link
Author

What if instead of renaming the symlinks you just place them in subfolders? It won’t fix the Launcher problem (there will still be only one eclipse) but at least they will be usable by navigating to the Applications folder or using Spotlight. Before I started using Cask I used to just put the different eclipse installations in the Applications directory and open them from there or have them pinned to the dock (another way to use eclipse if the symlinks are in subfolders).

Leo Jweda

On Jan 12, 2015, at 12:14, Vítor Galvão notifications@github.com wrote:

We’re aware of it, but that’s an upstream problem, really. Why do they all have the same name to begin with? What do people usually do with them?

We can’t simply start renaming them, as that can break expectations to users.


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

@tapeinosyne
Copy link
Contributor

We’re aware of it, but that’s an upstream problem, really. Why do they all have the same name to begin with? What do people usually do with them?

We can’t simply start renaming them, as that can break expectations to users.

We do rename the symlink for scala-ide, which is part of the Eclipse product family. While we should add a caveat to notify the user, I feel that it is acceptable as a workaround.

@vitorgalvao
Copy link
Member

It won’t fix the Launcher problem

I don’t know about other launchers, but in Alfred renaming symlinks wouldn’t solve the issue anyway, as it doesn’t follow them.

Before I started using Cask I used to just put the different eclipse installations in the Applications directory

They’d still have the same name, so there’s a step you’re skipping, there.

What if instead of renaming the symlinks you just place them in subfolders?

And in response

I feel that this is an acceptable workaround.

Very much agreed, although #5101 would be a better fit (but that could take a while to happen, if ever). If you submit a PR, we can discuss it better. Taking eclipse-jee as the example, something like app 'eclipse/Eclipse.app', :target => 'eclipse-jee/Eclipse.app' should be a good starting point.

We do rename the symlink for scala-ide

But that one also has the weight of having inconsistent branding, so renaming the app bundle’s link is a workaround that also prevents confusion. Putting the other ones in subfolders seems more appropriate.

@vitorgalvao
Copy link
Member

@leojweda Do you intend to submit a PR with the idea?

@vitorgalvao
Copy link
Member

Seems like there’s no interest in this. Closing.

@adidalal adidalal removed the awaiting user reply Issue needs response from a user. label Apr 12, 2016
@Homebrew Homebrew locked and limited conversation to collaborators May 8, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants