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 swi-prolog
is error-free.brew style --fix swi-prolog
reports no offenses.Additionally, if adding a new cask:
Named the cask according to the [token
reference](https://docs.brew.sh/Cask-Cookbook#token-reference).
There is already a core package named
swi-prolog
, but as far as I can tell from this document, the cast should also be namedswi-prolog
(though I originally was calling itswi-prolog-gui
).To make this work I had remove
swi-prolog
fromtap_migrations.json
. I'm thinking this should be safe, as this migration happend on Aug 22, 2016: bf9a703I'm thinking a caveat should also be added to
core/swi-prolog
similar tocore/wireshark
(I can open a PR for that to!):Checked the cask was not already refused (add your cask's name to the end of the search field).
Checked the cask is submitted to the correct repo.
brew audit --cask --new swi-prolog
worked successfully.I get two errors:
I'm not sure what to do about the unsigned issue, it is from the offical swi-prolog site though! Maybe open an issue for them to get it signed?
And for the name conflict, it seems like I should name it as
swi-prolog
the same aswireshark
.HOMEBREW_NO_INSTALL_FROM_API=1 brew install --cask swi-prolog
worked successfully.brew uninstall --cask swi-prolog
worked successfully.brew livecheck --cask swi-prolog
worked successfully.Hello all! The reason I'm adding this is the
swi-prolog
formula doesn't have GUI support! So you can't use the graphical debuggergtrace.
(it's very nice!)There are some issues though (commented about), that I would love help resolving:
swi-prolog
even though there is a formulaswi-prolog
? Or should it be something likeswi-prolog
? Currently audit is giving a duplicate name error. 😢tap_migrations.json
?Thanks y'all!