Restore 3dconnexion from homebrew-cask-drivers; update to 10.8.7 #206331
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Important: Do not tick a checkbox if you haven’t performed its action. Honesty is indispensable for a smooth review process.
In the following questions
<cask>
is the token of the cask you're submitting.After making any changes to a cask, existing or new, verify:
brew audit --cask --online <cask>
is error-free.brew style --fix <cask>
reports no offenses.Additionally, if adding a new cask:
brew audit --cask --new <cask>
worked successfully.HOMEBREW_NO_INSTALL_FROM_API=1 brew install --cask <cask>
worked successfully.brew uninstall --cask <cask>
worked successfully.I'm opening this as a draft for now, because I need a little help: after being installed, this doesn't work out-of-the-box, because it includes a macOS "Driver Extension." I couldn't find anything in the Homebrew docs about this, is there a particular programmatic way to handle this?
At the moment, the workaround is to manually launch the
3DconnexionHelper.app
that's included when this installs, which will then cause the system-prompt to enable the driver extension. After this, it will show up in System Preferences.The 3Dconnexion applications handle this, for the most part, prompting you to go into system prefs and enable it; but it doesn't appear in system prefs until you've launched the helper-app at least once:
Any feedback? Is there a best-practices for driver extensions?