After a long silence, Paru has been updated — a wrapper for pacman with AUR integration.
The update contains many major changes, mainly important for advanced users.
PKGBUILD repositories
The main feature of this release is the ability to integrate PKGBUILD repositories that are not based on AUR. You can now add them in paru.conf:
[repo_name] Url = https://path/to/git/repo
Then synchronize using paru -Sy —pkgbuilds.
You can also use Path = instead of Url = to specify a path on the local disk.
Paru will consider such a repository as a source of PKGBUILDs alongside AUR.
paru -S foo
PKGBUILD repositories have a higher priority than AUR. They can still use dependencies from AUR.
There is also a default PKGBUILD repository named . in the current directory. Roughly speaking, the following 'invisible strings' exist in paru.conf:
[.] Path = .
This allows for paru -S ./foo, where foo is the package name (not the path) in the current directory. This means that if you have a bunch of interdependent PKGBUILDs in the directory, you can build one using paru -S ./foo, and paru will resolve the dependencies.
Previously, paru -U could also be used to build a PKGBUILD in the current directory. This option has been renamed to paru -B … and now allows building multiple PKGBUILDs at once.
Chroot
—chroot now works without local repositories, although it still works better with them.
—interactive
paru foo has always been used for interactive searching and installation. Now there is also the —interactive flag, which works with other operations.
- paru foo is a synonym for paru -S —interactive foo.
- paru -R —interactive foo is used for interactive removal.
- paru -Ss/-Qs —interactive foo will issue an interactive prompt and then print the selected packages, so you can redirect the output to another command.
Source: linux.org.ru
