blob: a0ec2ab194d204f2f1e53125dab717a08cc55a1b (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
|
.TH "QUICKPKG" "1" "Dec 2005" "Portage 2.1" "Portage"
.SH NAME
quickpkg \- creates portage packages
.SH SYNOPSIS
.B quickpkg <list of pkgs>
.SH DESCRIPTION
.I quickpkg
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 \fBemerge\fR(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.
.br
The packages, after being created, will be placed in \fBPKGDIR\fR.
This variable is defined in \fBmake.conf\fR(5) and defaults to
/usr/portage/packages.
.SH OPTIONS
.TP
.B <list of packages>
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. This atom is of
the same form that you would give \fBemerge\fR if you wanted
to emerge something. See \fBebuild\fR(5) for full definition.
.SH "EXAMPLES"
.B quickpkg
/var/db/pkg/dev-python/pyogg-1.1
.br
.B quickpkg
planeshift
.br
.B quickpkg
=apache-1.3.27-r1
.br
.B quickpkg
=net-www/apache-2*
.SH "REPORTING BUGS"
Please report bugs via http://bugs.gentoo.org/
.SH AUTHORS
.nf
Terry Chan (original author)
Mike Frysinger <vapier@gentoo.org> (revamped version)
.fi
.SH "FILES"
.TP
.B /etc/make.conf
The \fBPKGDIR\fR variable is defined here.
.SH "SEE ALSO"
.BR ebuild (5),
.BR make.conf (5)
|
