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 that a repository in a Developer cache can still be selected
Țugui Dragoș11ff8bfb5168
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.mdindex 1cf498aa..e0993035 100644--- a/CONTRIBUTING.md+++ b/CONTRIBUTING.md@@ -171,9 +171,10 @@ Tests enforce these. If your change makes one of them fail, the rule is right an- **What may exist nowhere else is never selected for the user.** A folder with a wallet, a signing key, a passworddatabase, or a repository inside, one where an app keeps what may exist only on this Mac, or one Peel could notfinish reading, is shown with its reason and moves only when the user selects it with its own click: Select All,- `peel uninstall`, `peel orphans --remove`, and `peel projects --remove` pass it by (`SelectableRows.leftToTheClick`). The- one exception is a repository inside a folder its tool tags as a cache (`CACHEDIR.TAG`), such as Swift Package- Manager's `.build`, whose clones the tool makes again.+ `peel uninstall`, `peel orphans --remove`, and `peel projects --remove` pass it by (`SelectableRows.leftToTheClick`).+ A repository can still be selected in two places, since its tool clones it again: inside a folder the tool tags as a+ cache (`CACHEDIR.TAG`), such as Swift Package Manager's `.build`, and inside a cache on the Developer page, such as+ the packages Xcode checks out into DerivedData.- **The user's exclusions reach every scanner**, so an excluded item never appears in the first place.- **Resetting an app clears its settings, never the app.** It takes the app's own data only when the userselects it, needs the app to be quit, and inside a sandboxed app's container never touches `Documents`,diff --git a/SAFETY.md b/SAFETY.mdindex 3c3d93c0..4655b906 100644--- a/SAFETY.md+++ b/SAFETY.md@@ -233,10 +233,13 @@ shown with their size as "Unknown", never as zero, in every tool and in Historyread quickly may be exactly the one with work inside, and nothing is selected for you without saying how much it is. Atotal that leaves such a folder out reads "Over" what is known.-A repository inside a folder its tool tags as a cache (`CACHEDIR.TAG`) is the one exception: the tool says it makes-everything in there again. Swift Package Manager tags `.build`, where it clones a package's dependencies, and-`swift package reset` deletes that folder whole, so Build Artifacts can still select it. Carthage's checkouts, which-people commit in, carry no such tag and are never selected.+A repository can still be selected in two places, since its tool makes everything there again. One is a folder its+tool tags as a cache (`CACHEDIR.TAG`): Swift Package Manager tags `.build`, where it clones a package's+dependencies, and `swift package reset` deletes that folder whole, so Build Artifacts can still select it. The other+is a cache on the Developer page, a folder its tool's documentation or source shows to be a cache, such as the+packages Xcode checks out into DerivedData or the clones Cargo and Swift Package Manager keep, which the tool clones+again when it needs them. Carthage's checkouts in a project, which people commit in, carry no such tag and are never+selected.Build Artifacts selects what a build or a package manager makes again from the project's own files, such as`DerivedData`, `.build`, and `.next`, once Peel can tell that nothing in the project has changed for a week. That