Section: Portage (1)
Updated: Apr 2019
quickpkg - creates portage packages
quickpkg [options] <list of packages or package-sets>
can be utilized to quickly create a package for portage by
utilizing the files already on your filesystem. This package
then can be emerged on any system. To review syntax for
emerging binary packages, review emerge(1). The upside
of this process is that you don't have to wait for the package
to unpack, configure, compile, and install before you can have
the package ready to go. The downside is that the package will
contain the files that exist on your filesystem even if they have
modified since they were first installed.
The packages, after being created, will be placed in PKGDIR.
This variable is defined in make.conf(5) and defaults to
- <list of packages or package-sets>
Each package in the list can be of two forms. First you can
give it the full path to the installed entry in the virtual
database. That is, /var/db/pkg/<CATEGORY>/<PKG-VERSION>/.
The second form is a portage depend atom or a portage package
set. The atom or set is of the same form that you would give
emerge if you wanted to emerge something.
See ebuild(5) for full definition.
Causes the QUICKPKG_DEFAULT_OPTS environment variable to be ignored.
- --include-config < y | n >
Include all files protected by CONFIG_PROTECT (as a security precaution,
default is 'n').
- --include-unmodified-config < y | n >
Include files protected by CONFIG_PROTECT that have not been modified
since installation (as a security precaution, default is 'n').
The umask used during package creation (default is 0077).
Please report bugs via https://bugs.gentoo.org/
Terry Chan (original author)
Mike Frysinger <email@example.com> (revamped version)
The PKGDIR variable is defined here.
- REPORTING BUGS
- SEE ALSO
This document was created by
using the manual pages.
Time: 06:01:45 GMT, June 24, 2020