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

Artifact for Internet Plug-ins (New cask Google Earth Web Plugin) #5909

Closed
diimdeep opened this issue Aug 25, 2014 · 4 comments · Fixed by #5923
Closed

Artifact for Internet Plug-ins (New cask Google Earth Web Plugin) #5909

diimdeep opened this issue Aug 25, 2014 · 4 comments · Fixed by #5923

Comments

@diimdeep
Copy link
Contributor

I wanted to add cask for Google Earth Web Plugin, it is distributed as .plugin inside .dmg that usually goes to ~/Library/Internet Plug-Ins/, but I wont find Artifact(like qlplugin) for this type of cask, or any other way to describe installation task, I'm not sure, maybe I'm missing something.

@vitorgalvao
Copy link
Contributor

I believe we don’t have such artifact. Not a common case in the slightest, but I see no reason why it should be left out.

@rolandwalker
Copy link
Contributor

Hi!

The reason it was never put in (so far) is that most such plugins install via a pkg.

We can easily add it, though note that I plan to consolidate the various --prefpanedir-type command-line options into a single --librarydir.

@rolandwalker
Copy link
Contributor

@diimdeep we added this functionality in #5923. However, it will take a couple of weeks for the code to get into release. So, I've reopened this issue and am assigning myself, to remind me to ping you about that.

@rolandwalker rolandwalker self-assigned this Aug 26, 2014
@rolandwalker
Copy link
Contributor

The internet_plugin artifact is now in release (v0.40.0).

It is OK to use it in a Cask now.

@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

Successfully merging a pull request may close this issue.

4 participants