First, you need to identify which artifact is not being handled correctly anymore. It’s explicit in the error message: if it says It seems the App source…'
the problem is app
. The pattern is the same across all artifacts.
Fixing this error is typically easy, and requires only a bit of time on your part. Start by downloading the package for the cask: brew fetch {{cask_name}}
. The last line of output will inform you of the location of the download. Navigate there and manually unpack it. As an example, lets say the structure inside the archive is as follows:
.
├─ Files/SomeApp.app
├─ Files/script.sh
└─ README.md
Now, let's look at the cask (brew cat {{cask_name}}
):
(…)
app "SomeApp.app"
(…)
The cask was expecting SomeApp.app
to be in the top directory of the archive (see how it says simply SomeApp.app
) but the developer changed it to inside a Files
directory. All we have to do is update that line of the cask to follow the new structure: app 'Files/SomeApp.app'
.
Note that occasionally the app’s name changes completely (from SomeApp.app
to OtherApp.app
, let's say). In these instances, the filename of the cask itself, as well as its token, must also change. Consult the token reference
for complete instructions on the new name.
Help us by submitting a fix. If you get stumped, open an issue explaining your steps so far and where you’re having trouble.
此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。