Skip to content

armgit / peel

Public Imported from GitHub
0

Uninstall Mac apps with every file they leave behind, and see why each belongs. Free up space, fine-tune macOS, and set up Terminal.

SAFETY and README say exactly what Build Artifacts selects

Țugui Dragoș56a8fcff0344
diff --git a/README.md b/README.md
index 801c9dc8..f83e8b3b 100644
--- a/README.md
+++ b/README.md
@@ -89,7 +89,8 @@ Peel is free and open source, and it speaks English and 17 other languages.
packages, and what a tool keeps for you to install again (Vagrant boxes, Asset Store packages) are listed but
never selected for you, and toolchains or anything holding an account are never listed.
- **Build Artifacts:** what builds left in the folders you choose, like `node_modules`, `DerivedData`, and
- `target`. A project changed in the last 7 days is never selected for you.
+ `target`. A project changed in the last 7 days is never selected for you, and neither is a Python environment,
+ Terraform's `.terraform`, or a folder like `target` whose name says nothing on its own.
- **Duplicates:** files and whole folders with identical contents, compared with SHA-256. One copy is always kept.
- **Installers and Backups:** installers of apps you already have, macOS installers, device firmware, and what your
iPhone backups hold. Nothing is selected for you.
diff --git a/SAFETY.md b/SAFETY.md
index 31734313..94bb2f69 100644
--- a/SAFETY.md
+++ b/SAFETY.md
@@ -146,19 +146,26 @@ Peel itself is listed on its own page with what it keeps, and nothing of it can
apps. It is removed only by Remove Peel, in Settings, which takes its helper and login item away first.
Never selected for you, even when found: Xcode's archives of the apps you built and the symbols it copied from your
-devices, both needed to read crash reports, model weights, installed packages and virtual environments, the
-installers and boxes a tool keeps for you to install again, `/Users/Shared` (it belongs to every account, not just
-yours), a project you worked on this week, a folder with a repository, a wallet, or a signing key inside, a folder
-macOS would not let Peel read, and a folder Peel could not measure in time. Those last two are shown with their size
-as "Unknown", never as zero, in every tool and in History once they are moved: a folder too big to read quickly may
-be exactly the one with work inside, and nothing is selected for you without saying how much it is. A total that
-leaves such a folder out reads "Over" what is known.
+devices, both needed to read crash reports, model weights, the packages a tool keeps installed outside your projects,
+virtual environments, the installers and boxes a tool keeps for you to install again, `/Users/Shared` (it belongs to
+every account, not just yours), a project you worked on this week, a folder with a repository, a wallet, or a signing
+key inside, a folder macOS would not let Peel read, and a folder Peel could not measure in time. Those last two are
+shown with their size as "Unknown", never as zero, in every tool and in History once they are moved: a folder too big to
+read quickly may be exactly the one with work inside, and nothing is selected for you without saying how much it is. A
+total 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.
+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
+includes `node_modules` and `Pods`, which `npm install` and `pod install` put back from the project's `package.json` and
+`Podfile`. A Python environment (`.venv`, `venv`) is listed and never selected, since packages are often installed into
+one by hand, and so is Terraform's `.terraform`, which keeps the workspace you chose. A folder whose name says nothing
+on its own, such as `target` or `build`, is listed and never selected either.
+
Orphaned Files selects nothing for you, and its Select All and `peel orphans --remove` leave these folders out as
well: one in `/Users/Shared`, one with a repository, a wallet, or a signing key inside, or one Peel could not read
or measure in time, moves only when you select it yourself.