Do not use packers. Obsolete and obsolete. use Hooray AUR helper instead. https://www.ostechnix.com/yay-found-yet-another-reliable-aur-helper/
Not long ago we wrote an article about How to install Yaourt on Arch Linux. Yaourt is a pacman wrapper that can be used to install packages from the AUR. For those who do not know the AUR, this is a community-driven repository containing over 44,000 packages. Today, this tutorial describes another front end called Pacman. Packer. Packer is a wrapper for both Pacman and AUR. Like Yaourt, Packer also reduces the complexity of manually compiling and installing packages. You can install, update, search, and view information about packages in the main repository and the AUR. For other commands, such as removing packages, use pacman.
Recommended downloads – Free Cheat Sheet: “Linux Command Line Cheat Sheet”
In this short tutorial, let’s see how to install and use Packer on Arch Linux.
Install Packer on Arch Linux
First, install the required dependencies using the command.
$ sudo pacman -S base-devel fakeroot jshon expac git wget
:: There are 25 members in group base-devel: :: Repository core 1) autoconf 2) automake 3) binutils 4) bison 5) fakeroot 6) file 7) findutils 8) flex 9) gawk 10) gcc 11) gettext 12) grep 13) groff 14) gzip 15) libtool 16) m4 17) make 18) pacman 19) patch 20) pkg-config 21) sed 22) sudo 23) texinfo 24) util-linux 25) which Enter a selection (default=all):
Download PKGBUILD script from AUR.
$ wget https://aur.archlinux.org/cgit/aur.git/plain/PKGBUILD?h=packer
Rename the downloaded file.
$ mv PKGBUILD?h=packer PKGBUILD
Then compile the downloaded package by running the following command:
==> Making package: packer 20150808-1 (Tue May 10 18:39:36 IST 2016) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Cloning packer git repo... Cloning into bare repository '/home/sk/packer'... remote: Counting objects: 1505, done. remote: Compressing objects: 100% (5/5), done. remote: Total 1505 (delta 0), reused 0 (delta 0), pack-reused 1500 Receiving objects: 100% (1505/1505), 398.25 KiB | 204.00 KiB/s, done. Resolving deltas: 100% (530/530), done. Checking connectivity... done. ==> Validating source files with md5sums... packer ... Skipped ==> Extracting sources... -> Creating working copy of packer git repo... Cloning into 'packer'... done. ==> Starting pkgver()... ==> Updated version: packer 20160325-1 ==> Entering fakeroot environment... ==> Starting package()... ==> Tidying install... -> Removing libtool files... -> Purging unwanted files... -> Removing static library files... -> Stripping unneeded symbols from binaries and libraries... -> Compressing man and info pages... ==> Checking for packaging issue... ==> Creating package "packer"... -> Generating .PKGINFO file... -> Generating .BUILDINFO file... -> Generating .MTREE file... -> Compressing package... ==> Leaving fakeroot environment. ==> Finished making: packer 20160325-1 (Tue May 10 18:39:42 IST 2016)
The above command compiles and creates the Packer installation file.
To view new packer installation files, ls command:
Desktop packer PKGBUILD Downloads packer-20160325-1-any.pkg.tar.xz Soft_Backup Entertainment Personal src Pictures
As in the output above, packer-20160325-1-any.pkg.tar.xz Is the installation file.
Finally, install Packer using the command:
$ sudo pacman -U packer-*.pkg.tar.xz
If necessary, install the modificationscustomizepkg package and apply the customizepkg changes.
$ sudo pacman -S customizepkg
that’s it. Packer is installed.
You can now start installing, updating, and upgrading packages using Packer in the same way you would use Pacman. Use Pacman for other operations, such as removing packages. Packer usage is the same as Pacman. For information on using pacman, refer to the following guide: You can use the same guide for packers.
- Get started with Pacman
For example, to install a package:
$ packer -S
Packer can be used at any time as a regular user. You do not need to use sudo before every command. If the packer requires administrator privileges, you will be prompted for the root password.
That’s all for now. I will post another interesting article. Until then, look forward to OSTechNix. If you find this article useful, please share and support it on social and professional networks.