makepkg man page on Archlinux

Man page or keyword search:  
man Server   11224 pages
apropos Keyword Search (all sections)
Output format
Archlinux logo
[printable version]

MAKEPKG(8)			 Pacman Manual			    MAKEPKG(8)

       makepkg - package build utility

       makepkg [options]

       makepkg is a script to automate the building of packages. The
       requirements for using the script are a build-capable *nix platform and
       a custom build script for each package you wish to build (known as a
       PKGBUILD). See PKGBUILD(5) for details on creating your own build

       The advantage to a script-based build is that the work is only done
       once. Once you have the build script for a package, makepkg will do the
       rest: download and validate source files, check dependencies, configure
       the build-time settings, build the package, install the package into a
       temporary root, make customizations, generate meta-info, and package
       the whole thing up for pacman to use.

	   makepkg uses your current locale by default and does not unset it
	   when building packages. If you wish to share your build output with
	   others when seeking help or for other purposes, you may wish to run
	   "LC_ALL=C makepkg" so your logs and output are not localized.

	   Allow makepkg to run as root. This is for security purposes as it
	   is normally dangerous to do so. This will also disable use of
	   fakeroot and sudo.

       -A, --ignorearch
	   Ignore a missing or incomplete arch field in the build script. This
	   is for rebuilding packages from source when the PKGBUILD may be
	   slightly outdated and not updated with an arch=('yourarch') field.

       -c, --clean
	   Clean up leftover work files and directories after a successful

       --config <file>
	   Use an alternate config file instead of the /etc/makepkg.conf

       -d, --nodeps
	   Do not perform any dependency checks. This will let you override
	   and ignore any dependencies required. There is a good chance this
	   option will break the build process if all of the dependencies are
	   not installed.

       -e, --noextract
	   Do not extract source files or run the prepare() function (if
	   present); use whatever source already exists in the $srcdir/
	   directory. This is handy if you want to go into $srcdir/ and
	   manually patch or tweak code, then make a package out of the
	   result. Keep in mind that creating a patch may be a better solution
	   to allow others to use your PKGBUILD.

	   For each source file in the source array of PKGBUILD, download the
	   file if required and perform the integrity checks. No extraction or
	   build is performed. Useful for performing subsequent offline

       -f, --force
	   makepkg will not build a package if a built package already exists
	   in the PKGDEST (set in makepkg.conf(5)) directory, which may
	   default to the current directory. This allows the built package to
	   be overwritten.

       -g, --geninteg
	   For each source file in the source array of PKGBUILD, download the
	   file if required and generate integrity checks. The integrity
	   checks generated are determined by the checks present in the
	   PKGBUILD, falling back to the value of the INTEGRITY_CHECK array in
	   makepkg.conf(5) if these are absent This output can be redirected
	   into your PKGBUILD for source validation using "makepkg -g >>

	   Do not perform any integrity checks (checksum and PGP) on source

	   Do not verify checksums of source files.

	   Do not verify PGP signatures of source files.

       -h, --help
	   Output syntax and command line options.

	   When using VCS sources (PKGBUILD(5)) any currently checked out
	   source will not be updated to the latest revision.

       -i, --install
	   Install or upgrade the package after a successful build using

       -L, --log
	   Enable makepkg build logging. This will use the tee program to send
	   output of the build() function to both the console and to a text
	   file in the build directory named pkgname-pkgver-pkgrel-arch.log.
	   As mentioned above, the build log will be localized so you may want
	   to set your locale accordingly if sharing the log output with

       -m, --nocolor
	   Disable color in output messages.

       -o, --nobuild
	   Download and extract files, run the prepare() function, but do not
	   build them. Useful with the --noextract option if you wish to tweak
	   the files in $srcdir/ before building.

       -p <buildscript>
	   Read the package script buildscript instead of the PKGBUILD
	   default; see PKGBUILD(5).

       -r, --rmdeps
	   Upon successful build, remove any dependencies installed by makepkg
	   during dependency auto-resolution and installation when using -s.

       -R, --repackage
	   Repackage contents of the package without rebuilding the package.
	   This is useful if you forgot a depend or install file in your
	   PKGBUILD and the build itself will not change.

       -s, --syncdeps
	   Install missing dependencies using pacman. When build-time or
	   run-time dependencies are not found, pacman will try to resolve
	   them. If successful, the missing packages will be downloaded and

       -S, --source
	   Do not actually build the package, but build a source-only tarball
	   that does not include sources that can be fetched via a download
	   URL. This is useful for passing a single tarball to another program
	   such as a chroot, remote builder, or a tarball upload. Because
	   integrity checks are verified, all source files of the package need
	   to be present or downloadable.

       -V, --version
	   Display version information.

	   Do not actually build the package, but build a source-only tarball
	   that includes all sources, including those that are normally
	   download via makepkg. This is useful for passing a single tarball
	   to another program such as a chroot or remote builder. It will also
	   satisfy requirements of the GPL when distributing binary packages.

       --pkg <list>
	   Only build listed packages from a split package. Multiple packages
	   should be comma separated in the list. This option can be specified
	   multiple times.

	   Run the check() function in the PKGBUILD, overriding the setting in

	   Do not run the check() function in the PKGBUILD or handle the

	   Sign the resulting package with gpg, overriding the setting in

	   Do not create a signature for the built package.

       --key <key>
	   Specify a key to use when signing packages, overriding the GPGKEY
	   setting in makepkg.conf(5). If not specified in either location,
	   the default key from the keyring will be used.

	   (Passed to pacman) Prevent pacman from waiting for user input
	   before proceeding with operations.

	   (Passed to pacman) Tell pacman not to reinstall a target if it is
	   already up to date. (used with -i / --install).

	   (Passed to pacman) Install packages as non-explicitly installed
	   (used with -i / --install).

	   (Passed to pacman) Prevent pacman from displaying a progress bar;
	   useful if you are redirecting makepkg output to file.

       makepkg supports building development versions of packages without
       having to manually update the pkgver in the PKGBUILD. This was formerly
       done using the separate utility versionpkg. See PKGBUILD(5) for details
       on how to set up a development PKGBUILD.

	   The command that will be used to check for missing dependencies and
	   to install and remove packages. Pacman’s -Qq, -Rns, -S, -T, and -U
	   operations must be supported by this command. If the variable is
	   not set or empty, makepkg will fall back to ‘pacman’.

	   Folder where the resulting packages will be stored. Overrides the
	   corresponding value defined in makepkg.conf(5).

	   Folder where the downloaded sources will be stored. Overrides the
	   corresponding value defined in makepkg.conf(5).

       PACKAGER="John Doe <>"
	   String to identify the creator of the resulting package. Overrides
	   the corresponding value defined in makepkg.conf(5).

	   Folder where the package will be built. Overrides the corresponding
	   value defined in makepkg.conf(5).

       See makepkg.conf(5) for more details on configuring makepkg using the
       makepkg.conf file.

       makepkg.conf(5), PKGBUILD(5), pacman(8)

       See the pacman website at for current
       information on pacman and its related tools.

       Bugs? You must be kidding, there are no bugs in this software. But if
       we happen to be wrong, send us an email with as much detail as possible

       Current maintainers:

       ·   Allan McRae <>

       ·   Dan McGee <>

       ·   Dave Reisner <>

       Past major contributors:

       ·   Judd Vinet <>

       ·   Aurelien Foret <>

       ·   Aaron Griffin <>

       ·   Xavier Chantry <>

       ·   Nagy Gabor <>

       For additional contributors, use git shortlog -s on the pacman.git

Pacman 4.1.2			  2013-06-18			    MAKEPKG(8)

List of man pages available for Archlinux

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
Vote for polarhome
Free Shell Accounts :: the biggest list on the net