Difference between revisions of "ABS FAQ"

From ArchWiki
Jump to: navigation, search
(rm displaytitle; will not work)
(How do I install the package I just made?)
(26 intermediate revisions by 13 users not shown)
Line 1: Line 1:
[[Category:Package development (English)]]
+
[[Category:Package development]]
[[Category:About Arch (English)]]
+
[[Category:About Arch]]
[[Category:HOWTOs (English)]]
+
[[ja:ABS FAQ]]
 +
[[ru:ABS FAQ]]
 +
{{merge|ABS}}
 
{{Article summary start}}
 
{{Article summary start}}
 
{{Article summary text|Very simple answers to questions about the Arch Build System and making your own Arch Linux packages.}}
 
{{Article summary text|Very simple answers to questions about the Arch Build System and making your own Arch Linux packages.}}
Line 14: Line 16:
 
== What is the ABS? ==
 
== What is the ABS? ==
  
"ABS" stands for [[Arch Build System]]. It's the way you create and install Arch Linux packages.
+
"ABS" stands for [[Arch Build System]]. It is a convenient way to create and install Arch Linux packages.
  
 
== What do people mean when they say "Use ABS"? ==
 
== What do people mean when they say "Use ABS"? ==
  
They mean, "Make and install an Arch Linux package". If you want to learn how to do this yourself, then keep reading. It's easy!
+
They mean, "Make and install an Arch Linux package using the provided Arch Linux 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 packages that I install using [[pacman]]? ==
+
== How do the Arch Linux developers create all of those binary packages that I install using [[pacman]]? ==
  
Arch Linux packages are created by using a [[PKGBUILD]] file. A PKGBUILD file is a Bash script that contains:
+
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.
 
*The name of the package, the version number, and lots of other information.
 
*Instructions for downloading, compiling, and installing the software package.
 
*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? ==
 
== Can I get a copy of the PKGBUILD files that the Arch Linux developers use? ==
  
Sure! Install the program {{filename|abs}}:
+
Sure! Install the program {{pkg|abs}}:
  
 
  # pacman -S abs
 
  # pacman -S abs
Line 37: Line 41:
 
  # abs
 
  # abs
  
You now have every official Arch Linux PKGBUILD file in {{filename|/var/abs}}.
+
You now have every official Arch Linux PKGBUILD file in {{ic|/var/abs}}.
  
 
== What do I do to make a package? ==
 
== What do I do to make a package? ==
  
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 [http://www.archlinux.org/packages/core/i686/vi/ vi], just like the one you can install using pacman. Copy the PKGBUILD from {{filename|/var/abs}} to a new directory:
+
First, make sure you have all of the development tools installed:
  
  $ cp -r /var/abs/core/vi ~/vi
+
  # pacman -S base-devel
  
Now go to your new directory:
+
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 {{pkg|vi}}, just like the one you can install using pacman. Copy the PKGBUILD from {{ic|/var/abs}} to a new directory:
  
  $ cd ~/vi
+
  $ cp -r /var/abs/core/vi ~/vi
  
Make sure you have all of the development tools installed:
+
Go to your new directory, and edit the PKGBUILD to your desired specifications with your text editor of choice.
 
+
# pacman -S base-devel
+
  
 
Use the [[makepkg]] command to make a package:
 
Use the [[makepkg]] command to make a package:
Line 57: Line 59:
 
  $ makepkg
 
  $ makepkg
  
That's it! You now have a {{filename|.pkg.tar.gz}} package for vi.
+
That's it! You now have a {{ic|.pkg.tar.xz}} package for vi.
  
== What are all of those other files under {{filename|/var/abs}}? ==
+
== What are all of those other files under {{ic|/var/abs}}? ==
  
 
Sometimes a PKGBUILD uses patches, or includes default settings files and examples.
 
Sometimes a PKGBUILD uses patches, or includes default settings files and examples.
Line 67: Line 69:
 
Use pacman:
 
Use pacman:
  
  # pacman -U yourpackagename.pkg.tar.gz
+
  # pacman -U yourpackagename.pkg.tar.xz
  
 
The actual name of the file depends on the name of the package, the version number, and what processor architecture you are using.
 
The actual name of the file depends on the name of the package, the version number, and what processor architecture you are using.
Line 73: Line 75:
 
== How do I make my own PKGBUILD file? ==
 
== How do I make my own PKGBUILD file? ==
  
You can just copy one from {{filename|/var/abs}} and modify it. You can read more about PKGBUILD files [[Creating Packages | here]].
+
You can copy an example PKGBUILD file from {{ic|/usr/share/pacman}} or {{ic|/var/abs}} and modify it. You can read more about PKGBUILD files [[Creating Packages | here]].
  
 
== Can somebody make a PKGBUILD file for me for a piece of software I want to use? ==
 
== Can somebody make a PKGBUILD file for me for a piece of software I want to use? ==
  
There's a good chance someone already did! Look in the "AUR", or [[Arch User Repository]]. ([http://aur.archlinux.org/]). You will find PKGBUILD files that other Arch Linux users made. You can also submit PKGBUILD files that you make yourself.
+
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 an [[AUR helper]] program. They are used to make it easy to find and install packages from the AUR. There are many different AUR helpers. For example, [http://aur.archlinux.org/packages.php?ID=33378 packer] is similar to pacman in functionality and is pretty easy to use.
+

Revision as of 23:34, 21 July 2013

Merge-arrows-2.pngThis article or section is a candidate for merging with ABS.Merge-arrows-2.png

Notes: please use the second argument of the template to provide more detailed indications. (Discuss in Talk:ABS FAQ#)
Template:Article summary start

Template:Article summary text Template:Article summary heading Template:Article summary wiki Template:Article summary wiki Template:Article summary wiki Template:Article summary wiki Template:Article summary wiki Template:Article summary end

What is the ABS?

"ABS" stands for Arch Build System. It is a convenient way to create and install Arch Linux packages.

What do people mean when they say "Use ABS"?

They mean, "Make and install an Arch Linux package using the provided Arch Linux 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 abs:

# pacman -S abs

And then run it as root:

# abs

You now have every official Arch Linux PKGBUILD file in /var/abs.

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 vi, just like the one you can install using pacman. Copy the PKGBUILD from /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:

$ makepkg

That's it! You now have a .pkg.tar.xz package for vi.

What are all of those other files under /var/abs?

Sometimes a PKGBUILD uses patches, or includes default settings files and examples.

How do I install the package I just made?

Use pacman:

# pacman -U yourpackagename.pkg.tar.xz

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 copy an example PKGBUILD file from /usr/share/pacman or /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.