|Summary help replacing me|
|Very simple answers to questions about the Arch Build System and making your own Arch Linux packages.|
|Arch Build System|
|Arch User Repository|
- 1 What is the ABS?
- 2 What do people mean when they say "Use ABS"?
- 3 How do the Arch Linux developers create all of those binary packages that I install using pacman?
- 4 Can I get a copy of the PKGBUILD files that the Arch Linux developers use?
- 5 What do I do to make a package?
- 6 What are all of those other files under /var/abs?
- 7 How do I install the package I just made?
- 8 How do I make my own PKGBUILD file?
- 9 Can somebody make a PKGBUILD file for me for a piece of software I want to use?
- 10 Isn't there an easier way to install packages from the AUR?
- 11 Installing to /usr/local: adding appropriate PATH entries
What is the ABS?
"ABS" stands for Arch Build System. It is a convenient way to create and install Arch Linux packages from source.
What do people mean when they say "Use ABS"?
They mean, "Make and install an Arch Linux package from source, using the provided Arch tools". If you want to learn how to do this yourself, then keep reading. It's easy!
How do the Arch Linux developers create all of those binary packages that I install using pacman?
Arch Linux packages are created by first writing a PKGBUILD file. A PKGBUILD file is a Bash script that contains:
- The name of the package, the version number, and lots of other information.
- Instructions for downloading, compiling, and installing the software package.
The newly written PKGBUILD file is then used by the makepkg program which uses the instructions contained within it to create a pacman-installable, binary package with the extenstion '.pkg.tar.xz'.
Can I get a copy of the PKGBUILD files that the Arch Linux developers use?
Sure! Install the program:
# pacman -S abs
And then run it as root:
You now have every official Arch Linux PKGBUILD file in
What do I do to make a package?
First, make sure you have all of the development tools installed:
# pacman -S base-devel
Now, all you need is a PKGBUILD file. I recommend that you make packages in a new directory. Let's say you want to make your own package for
/var/abs to a new directory:
$ cp -r /var/abs/core/vi ~/vi
Go to your new directory, and edit the PKGBUILD to your desired specifications with your text editor of choice.
Use the makepkg command to make a package:
That's it! You now have a
.pkg.tar.xz package for vi.
What are all of those other files under
Sometimes a PKGBUILD uses patches, or includes default settings files and examples.
How do I install the package I just made?
# pacman -U yourpackagename.pkg.tar.gz
The actual name of the file depends on the name of the package, the version number, and what processor architecture you are using.
How do I make my own PKGBUILD file?
You can just copy one from
/var/abs and modify it. You can read more about PKGBUILD files here.
Can somebody make a PKGBUILD file for me for a piece of software I want to use?
There is a good chance someone already did! Look in the "AUR", or Arch User Repository. You will find PKGBUILD files that other Arch Linux users made. You can also submit PKGBUILD files that you make yourself.
Isn't there an easier way to install packages from the AUR?
Yes, you can use one of the existing AUR helper program that makes it easy to find and install packages from the AUR.
/usr/local: adding appropriate PATH entries
You may want to consider exporting the following paths (e.g. to
~/.bash_profile) if you choose to build and install to
export PATH=$PATH:/usr/local/bin:/usr/local/sbin export PKG_CONFIG_PATH=$PKG_CONFIG_PATH:/usr/local/lib/pkgconfig export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib