title: pacopts author: Eric Vidal email@example.com
pacopts is a system maintainer helper
pacopts [ -h ] [ -z ] [ -v verbosity ] origin|service|aur <target> <arguments>
pacopts is a utility script written in bash which helps you to find the origin of the repositories for an installed package, to find a 66 frontend service file for software and to maintain/manage AUR packages using cower software.
111 system call failed
-h : prints this help.
-z : use color.
-v verbosity : increases/decreases the verbosity of the command.
1 : only print error messages. This is the default.
2 : also print warning messages.
3 : also print tracing messages.
4 : also print debugging messages.
Check origin of arguments as package names coming from a given target, where the target can be any valid repository name set at pacman.conf configuration file. If target is empty, obcore repository is used by default. If arguments is empty, all installed packages are checked from repositories set by target. Also, arguments can be a list of packages separated by space. Pacman queries versions of a package, not the origin of the package. For instance pacman won't know the origin of an identical package with the same version on differents repositories. The package version, or at least the release, need to be different to allow pacman to find it. For example, if you build a package from abs without changing the version/release, pacman can not find the original repository, and so pacopts can not find it either.
Check if a service-file exists for a given target, where target is the name of the package to check. If target is empty, all installed packages on the system will be checked. It only returns the name of the service frontend file that is not installed yet but exists in the observice repository. Also, target can be a list of packages separate by space.
pacopts <options> aur <aur_options> <target> <arguments> Maintain/install packages coming from AUR. It must be run with normal user privileges to avoid trouble on your system when a package is built. The file $HOME/.config/cower/config must exist even if empty. This file can be a simple copy of /usr/share/doc/cower/config, the cower configuration file. If the file doesn't exist, pacopts copies the sample coming from cower at $HOME/.config/cower/config. pacopts accepts any extra arguments coming from cower (see man cower) except for the command build, install and upgrade. However, to avoid conflicts between pacopts options and cower options, the long options must be used for cower. Short options have no effect. pacopts aur -i retrovol –format=%D pacopts aur -i retrovol clipit –format=%D The cower arguments help can be called under the command info, search, msearch, download, update by entering –help.
-i : show information about package.
-s : search package in AUR repositories.
-m : search for package maintained by a named maintainer. This is a synonym for searching with –by=maintainer.
-d : download the PKGBUILD of the package. The working directory where the PKGBUILD is downloaded is set by the variable TargetDir at $HOME/.config/cower/config file. If this variable is empty, /tmp is the default.
-u : check if packages are out of date. If you leave the target blank, pacopts checks for all installed packages on your system.
-U : download,build and install an outdated package. If you leave the target blank, pacopts does the same for all installed packages on your system.
-b : download the PKGBUILD of the package then build it. The AUR dependencies for the given package are not checked. The working directory where the PKGBUILD is downloaded is set by the variable TargetDir at $HOME/.config/cower/config file. If this variable is empty, /tmp is the default.
-I : download, build and install the package. If a dependency coming from AUR is detected, the script runs again the same scheme (download, build, install) for the dependency. This is done recursively.
/etc/obarun/pacopts.conf: configuration file for pacopts.
$HOME/.config/cower/config: configuration file for cower. This file is a simple copy of /usr/share/doc/cower/config. Also, the file can be empty but needs to exist.