Tweak code style and documentation wording

This commit is contained in:
Mike McQuaid 2023-05-29 08:59:35 +01:00 committed by GitHub
parent f43847516d
commit 98dd8610ae
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 4 additions and 3 deletions

View File

@ -249,6 +249,7 @@ module Cask
This may result in some configurations (like notification settings or location in the Dock/Launchpad) being lost. This may result in some configurations (like notification settings or location in the Dock/Launchpad) being lost.
To fix this, go to Settings > Security and Privacy > App Management and turn on the switch for your terminal. To fix this, go to Settings > Security and Privacy > App Management and turn on the switch for your terminal.
EOF EOF
false false
end end
end end

View File

@ -221,8 +221,8 @@ Or use the `--greedy` flag:
Refer to the `upgrade` section of the [`brew` manual page](Manpage.md) for more details. Refer to the `upgrade` section of the [`brew` manual page](Manpage.md) for more details.
## Why do my apps lose their Dock position / Launchpad position / permission settings when I run `brew upgrade`? ## Why do my cask apps lose their Dock position / Launchpad position / permission settings when I run `brew upgrade`?
Homebrew has two possible strategies to update apps: uninstalling the old version and reinstalling the new one, or replacing the contents of the app with the new contents. With the uninstall/reinstall strategy, [macOS thinks the app is being deleted without any intent to reinstall it](https://github.com/Homebrew/brew/pull/15138), and so it removes some internal metadata for the old app, including where it appears in the Dock and Launchpad and which permissions it's been granted. The content replacement strategy works around this by treating the upgrade as an in-place upgrade. However, starting in macOS Ventura, these in-place upgrades are only allowed when the updater application (in this case, the terminal running Homebrew) has [certain permissions granted](https://github.com/Homebrew/brew/pull/15483). Either the "App Management" or "Full Disk Access" permission will suffice. Homebrew has two possible strategies to update cask apps: uninstalling the old version and reinstalling the new one, or replacing the contents of the app with the new contents. With the uninstall/reinstall strategy, [macOS thinks the app is being deleted without any intent to reinstall it](https://github.com/Homebrew/brew/pull/15138), and so it removes some internal metadata for the old app, including where it appears in the Dock and Launchpad and which permissions it's been granted. The content replacement strategy works around this by treating the upgrade as an in-place upgrade. However, starting in macOS Ventura, these in-place upgrades are only allowed when the updater application (in this case, the terminal running Homebrew) has [certain permissions granted](https://github.com/Homebrew/brew/pull/15483). Either the "App Management" or "Full Disk Access" permission will suffice.
Homebrew defaults to in-place upgrades when it has the necessary permissions. Otherwise, it will use the uninstall/reinstall strategy. Homebrew defaults to in-place upgrades when it has the necessary permissions. Otherwise, it will use the uninstall/reinstall strategy.