Removing a package
In AEL, the Agent Engineering Language, ael pack remove (command names may change before launch) will remove a package that a scope declares, update its lock file and remove the installed files it no longer needs.
Status
Planned for AEL Beta 0.0.1. AEL is not available yet.
Package names on this page are preview naming and may change before launch.
Usage
ael pack remove server/http
ael pack remove server/http --scope src/api
| Argument or option | Meaning |
|---|---|
<name> | The package to remove, as pack.ael names it. |
--scope <folder> | Remove it from that folder's manifest. Without it, the manifest that covers the folder you are in. |
--json | A machine-readable report of the change. |
What it removes
It will remove:
- The package's entry in that scope's
pack.ael. - Its record in
pack.lock, and its installed files in.package/. - Packages it brought in that nothing else in the scope needs any more.
Packages that other packages still need will stay installed, and the command will say which ones and why.
It will never edit your source
If a file still selects the package with refer … select …, ael pack remove will leave that file as it is. The next ael check will fail and name the reference, so you remove it deliberately. The command will list the references it found.
Folders below
Removing a package from one manifest may change what the folders below it use. A folder that relied on this declaration may now use a declaration further up, or no longer have the package at all. The command will report, for each such folder, which manifest it now uses. It will never keep a removed declaration alive silently.
What it never touches
It will never touch:
- Data your program works with, such as datasets, calibration files and checkpoints.
- Deployment data, running programs and services, and programs you installed yourself, such as runtimes for the tools your agents call.
- The manifests and installed packages of other scopes.
- The shared package cache: to clear cached files that nothing uses, see Pruning the package cache.
Changes will be atomic
The manifest, the lock file and the installed packages will change together. If the removal is interrupted, the scope will stay as it was or be completed by the next package command, or by ael pack repair.
Related
- Listing packages: which packages are declared, installed and used.
- Why a package is in a project: what still needs a package.