Pruning the package cache
In AEL, the Agent Engineering Language, package files that your machine has fetched and verified are kept in a shared package cache, so the same file is not fetched twice for two projects. ael pack cache prune removes cached package files that nothing uses any more.
Usage
ael pack cache prune
ael pack cache prune --json
| Option | Meaning |
|---|---|
--json | A machine-readable report of what was removed. |
What it removes
Only package files in the shared cache that nothing refers to any more, such as copies left behind after an update or a removal.
The report lists every file it removed.
What it never touches
It never touches:
- Your source files.
- Any project's
pack.ael,pack.lockor installed packages in.package/. - Deployment data, and data your programs work with.
Programs you have built never read the cache: nothing downloads or loads from it when a program starts.
Removing a package or clearing the cache
ael pack cache prune is not how you stop using a package. To remove a package from a project, use ael pack remove, which changes the project's manifest, lock file and installed packages. Pruning afterwards only frees the space the cached copy took.
After pruning
A pruned file is fetched and verified again the next time a project needs it. On a machine without network access, a pruned file is gone until you bring it back, for example from a folder exported with ael pack vendor. Prune with care before working offline: ael pack install --offline can use only what is still on the machine.
Related
- Package commands: the network rules of every package command.
- Exporting for offline builds: keeping package files for isolated machines.