We've already seen how updating works when you install a package from a cache and the contents of a cache changes. There is a simple feature in Pacman 3 that lets you solve two common types of problem that can come up:
% pacman -lc trusted.cachesand
% pacman -l trusted.caches:nEdit -d srcto see what we mean. Similarly, any file ending in .caches on your local system or at a remote site can be treated as a single cache. For example, make a file called ~yourname/test.caches containing:
# # test # BU Pacmanand do
% pacman -get ~yourname/test.caches:nEdit % pacman -d up -land you will see something like
[*] nEdit, update from [~yourname/test.caches]Since you've installed nEdit from ~yourname/test.caches instead of directly from BU, the cache ~yourname/test.caches is tested for updates. This shows that your package nEdit originally comes from the cache BU but the cache ~yourname/test.caches is tested for updates.