version 1 showing authors affecting page license.
.
Rev |
Author |
# |
Line |
1 |
perry |
1 |
DH_INSTALL |
|
|
2 |
!!!DH_INSTALL |
|
|
3 |
NAME |
|
|
4 |
SYNOPSIS |
|
|
5 |
DESCRIPTION |
|
|
6 |
OPTIONS |
|
|
7 |
SEE ALSO |
|
|
8 |
AUTHOR |
|
|
9 |
---- |
|
|
10 |
!!NAME |
|
|
11 |
|
|
|
12 |
|
|
|
13 |
dh_install - install files into package build directories |
|
|
14 |
!!SYNOPSIS |
|
|
15 |
|
|
|
16 |
|
|
|
17 |
__dh_install__ [[__-X__''item''] [[''debhelper |
|
|
18 |
options''] [[''file [[...] dest''] |
|
|
19 |
!!DESCRIPTION |
|
|
20 |
|
|
|
21 |
|
|
|
22 |
dh_install is a debhelper program that handles installing |
|
|
23 |
files into package build directories. There are many |
|
|
24 |
dh_install* commands that handle installing specific types |
|
|
25 |
of files such as documentation, examples, man pages, and so |
|
|
26 |
on, and they should be used when possible as they often have |
|
|
27 |
extra intelligence for those particular tasks. dh_install, |
|
|
28 |
then, is useful for installing everything else, for which no |
|
|
29 |
particular intelligence is needed. It is a replacement for |
|
|
30 |
the old dh_movefiles command. |
|
|
31 |
|
|
|
32 |
|
|
|
33 |
Files named debian/package.install list the files to install |
|
|
34 |
into each package and where they should be installed to. The |
|
|
35 |
format is a set of lines, where each line lists a file or |
|
|
36 |
files to install, and at the end of the line tells the |
|
|
37 |
directory it should be installed in. The name of the files |
|
|
38 |
(or directories) to install should be given relative to the |
|
|
39 |
current directory, while the installation directory is given |
|
|
40 |
relative to the package build directory. You may use |
|
|
41 |
wildcards in the names of the files to install (in v3 mode |
|
|
42 |
and above). |
|
|
43 |
|
|
|
44 |
|
|
|
45 |
This program may be used in one of two ways. If you just |
|
|
46 |
have a file or two that the upstream Makefile does not |
|
|
47 |
install for you, you can run dh_install on them to move them |
|
|
48 |
into place. On the other hand, maybe you have a large |
|
|
49 |
package that builds multiple binary packages. You can use |
|
|
50 |
the upstream Makefile to install it all into debian/tmp, and |
|
|
51 |
then use dh_install to copy directories and files from there |
|
|
52 |
into the proper package build directories. |
|
|
53 |
!!OPTIONS |
|
|
54 |
|
|
|
55 |
|
|
|
56 |
__-Xitem__, __--exclude=item__ |
|
|
57 |
|
|
|
58 |
|
|
|
59 |
Exclude files that contain ``item'' anywhere in their |
|
|
60 |
filename from being installed. |
|
|
61 |
|
|
|
62 |
|
|
|
63 |
__--autodest__ |
|
|
64 |
|
|
|
65 |
|
|
|
66 |
Guess as the destination directory to install things to. If |
|
|
67 |
this is specified, you should not list destination |
|
|
68 |
directories in debian/package.install files or on the |
|
|
69 |
command line. Instead, dh_install will guess as |
|
|
70 |
follows: |
|
|
71 |
|
|
|
72 |
|
|
|
73 |
Strip off debian/tmp from the front of the filename, of it |
|
|
74 |
is present, and install into the dirname of the filename. So |
|
|
75 |
if the filename is debian/tmp/usr/bin, then that directory |
|
|
76 |
will be copied to debian/package/usr/. If the filename is |
|
|
77 |
debian/tmp/etc/passwd, it will be copied to |
|
|
78 |
debian/package/etc/. |
|
|
79 |
|
|
|
80 |
|
|
|
81 |
Note that if you list only a filename on a line by itself in |
|
|
82 |
a debian/package.install file, with no explicit destination, |
|
|
83 |
then dh_install will automatically guess the destination |
|
|
84 |
even if this flag is not set. |
|
|
85 |
|
|
|
86 |
|
|
|
87 |
''file [[...] dest'' |
|
|
88 |
|
|
|
89 |
|
|
|
90 |
Lists files (or directories) to install and where to install |
|
|
91 |
them to. The files will be installed into the first package |
|
|
92 |
dh_install acts on. |
|
|
93 |
!!SEE ALSO |
|
|
94 |
|
|
|
95 |
|
|
|
96 |
debhelper(1) |
|
|
97 |
|
|
|
98 |
|
|
|
99 |
This program is a part of debhelper. |
|
|
100 |
!!AUTHOR |
|
|
101 |
|
|
|
102 |
|
|
|
103 |
Joey Hess |
|
|
104 |
---- |