Default local kmpkg binary cache

By default, kmpkg creates a local binary cache. This saves time when installing a package that has been previously installed in the same machine.

The location of the default binary cache depends on your operating system.

powershell

By default, binary caching is enabled at the first valid location among the following:

• The location specified by the KMPKG_DEFAULT_BINARY_CACHE environment variable
• %LOCALAPPDATA%\kmpkg\archives
• %APPDATA%\kmpkg\archives

bash

By default, binary caching is enabled at the first valid location among the following:

• The location specified by the KMPKG_DEFAULT_BINARY_CACHE environment variable
• $XDG_CACHE_HOME/kmpkg/archives
• $HOME/.cache/kmpkg/archives

Use the KMPKG_DEFAULT_BINARY_CACHE environment variable to change the default binary cache location.

The default binary cache uses a files provider. This type of binary cache provider stores binary packages as compressed archives in a filesystem directory.

Disabling the default binary cache

To disable the default binary cache, set the KMPKG_BINARY_SOURCES environment variable to clear.

powershell

$env:KMPKG_BINARY_SOURCES="clear"

cmd

set KMPKG_BINARY_SOURCES=clear

bash

export KMPKG_BINARY_SOURCES=clear

Next steps

Set up a local binary cache

Here are other tasks to try next:

• Change the default binary cache location
• Set up a local binary cache
• Set up a binary cache using a NuGet feed
• Set up a binary cache in your GitHub Actions workflow using GitHub Packages