-
-
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
Add Sound Blaster Control App #83961
Conversation
Failing with
|
@iMonZ Where you going to take a look at this, or should we proceed with closing this out? |
Oh I’m sorry I thought this was closed!
Im fixing this today
… Am 12.07.2020 um 01:08 schrieb Randall ***@***.***>:
@iMonZ Where you going to take a look at this, or should we proceed with closing this out?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Needs to be submitted to homebrew/cask-drivers, it seems. We define drivers as:
Note that repo has special naming rules. What are the names of the apps this installs under |
It‘s the same kind as #83746 and this is also an Cask (because this is an control App for this device)
This will be automatically uninstalled with the installer script! |
|
Which looks like it too should be in the drivers repo.
If it controls a device, it definitely belongs in the other repo.
Not why I’m asking. I really do want the names of the apps. |
@@ -0,0 +1,19 @@ | |||
cask 'sound-blaster-control' do |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would be more compliant with the rules to be sound-blaster-control-panel
.
@iMonZ, please rebase this and adjust the style to the new rules. |
Definitely looks like it belongs in homebrew/cask-drivers. I’ll move the other cask. There’s been no reply on this for over a month, so I’ll close it. It can be resubmitted to the correct repo with the requested fixes.
User rebases remove the ability to see what changed between commits, which means we have to reevaluate the whole cask every time. Since cask submissions should always be a single commit, it’s better if we do it ourselves through the Github interface or a script (that’s an example). |
Important: Do not tick a checkbox if you haven’t performed its action. Honesty is indispensable for a smooth review process.
After making all changes to a cask, verify:
brew cask audit --download {{cask_file}}
is error-free.brew cask style --fix {{cask_file}}
reports no offenses.Additionally, if adding a new cask:
brew cask install {{cask_file}}
worked successfully.brew cask uninstall {{cask_file}}
worked successfully.