The most basic operations of "getting" and removing packages is often all you need to know about Pacman to get software that you are interested in. Sometimes, however, it helps to have finer controls over these operations. This is provided by
% pacman -fetch BU:nEdit Pacman:Pacman % pacman -l [ ] nEdit, in cache [/home/youssef/Pacman/work] [ ] Pacman, in cache [/home/youssef/Pacman/work]this tells you that all dependencies have been resolved and that you may be able to do the installation. To install the packages, you can do % pacman -install BU:nEdit Pacman:Pacman or simply
% pacman -installto install all of the top level packages in the installation. You will then see
% pacman -l [*] nEdit, in cache [/home/youssef/Pacman/work] [*] Pacman, in cache [/home/youssef/Pacman/work]that the installation has worked but no setup scripts have appeared. Finally, do
% pacman -setupand you will see that the setup scripts appear. To avoid confusion, -setup always applies to an entire installation, so if you see setup scripts, it automatically means that Pacman has concluded that all of the software in the installation has successfully installed and that the packages are consistent.
Part of the point of separating -setup is to allow installations that contain inconsistent packages. This is useful, for example, if you want to have a single installation that contains multiple incompatible versions of the same package. See the versions section for of the documentation for more details about this.