Uninstall Mac apps with every file they leave behind, and see why each belongs. Free up space, fine-tune macOS, and set up Terminal.
Swift cache-cleanercleanerclideveloper-toolsdisk-cleanupdisk-spaceduplicate-finderhomebrewliquid-glassmac-cleanermacosmacos-appmacos-golden-gatemacos-tahoemacos-tweaksswiftswiftuiterminal-themesuninstalluninstaller
Say in ARCHITECTURE.md how a launch job is matched
Țugui Dragoș80c07f7ca4aa
diff --git a/ARCHITECTURE.md b/ARCHITECTURE.mdindex a0e67266..a94d8d64 100644--- a/ARCHITECTURE.md+++ b/ARCHITECTURE.md@@ -72,7 +72,9 @@ Take the most common case, uninstalling an app. Every other page follows the sam2. **Match.** For each file, `LeftoverMatcher` weighs the evidence that it belongs to the app: its bundleidentifier, the identifiers of what the app embeds, its application groups, its signing team, its name. Aplug-in and a container named by a UUID are also weighed by the identifier they declare: a plug-in's name- says what it does and a UUID says nothing, so the identifier decides whose they are. The answer is a+ says what it does and a UUID says nothing, so the identifier decides whose they are. A launch job is weighed+ by the program it runs, since anyone can name its file: a job that runs a program inside the app is the+ app's, and one that runs a program inside another installed app is that app's. The answer is a`LeftoverMatch`: a confidence (`certain`, `likely`, or `possible`), the reason, the other installed apps thatclaim the file too (with the apps of the same maker that macOS knows outside the Applications folders), theother copies of the app that use it (any macOS knows, wherever they are, named by their place), and, when Peel