Offline Mode¶

Collider maintains a local cache so you can build without network access.

Cache Location¶

The cache lives at ~/.config/collider/cache/ (or $XDG_CONFIG_HOME/collider/cache/) and contains two directories:

Hash-keyed archive storage deduplicates identical content across packages.

How the Cache is Populated¶

When Collider downloads a wrap or archive during pkg add, pkg upgrade, install, or lock, it stores a copy in the cache automatically. No extra command is needed.

Using Offline Mode¶

Pass --offline to any command that resolves packages:

collider pkg add my-lib --offline
collider pkg upgrade --offline
collider lock --offline
collider install --offline

In offline mode, Collider:

• Refuses to make network requests.
• Resolves packages only from cached wraps.
• Allows file:// archive URLs (local paths).
• During transitive resolution, checks the local wrap cache for each dependency before attempting network access. If a cached wrap exists, it is used for scanning without going online. If no cache entry is found, the dependency is skipped with a warning.
• When installing from a lockfile, falls back to the local cache if the origin repository requires network access and emits a warning that origin provenance cannot be verified. The wrap_hash check still ensures content integrity.

Meson Package Cache¶

On install, Collider populates subprojects/packagecache/ with the source and patch archives referenced by each wrap. This is the directory Meson checks for cached downloads, so subsequent meson setup calls work without network access.

Wrap File Requirements¶

For offline mode to work, wrap files must include:

• source_url, source_filename, and source_hash (always required).
• patch_url, patch_filename, and patch_hash: optional, but if one is present all three must be present.