diff options
| author | joey <joey> | 2000-10-28 06:13:50 +0000 |
|---|---|---|
| committer | joey <joey> | 2000-10-28 06:13:50 +0000 |
| commit | 4c98da4fc74be80721e50f808b7a0b9a327feb64 (patch) | |
| tree | 26fd669ce8c5c65d9a1b998d4d34828878d14c8d /dh_movefiles.1 | |
| parent | 307194e33ae1856238c94a07818d9dfd4712f52f (diff) | |
r379: * dh_movefiles.1: well I thought it was quite obvious why it always used
debian/tmp, but it's a faq. Added some explanation. By the way, since
there now exists a documented way to use dh_movefiles that does not
have problems with empty directories that get left behind and so on, I
think this Closes: #17111, #51985
Diffstat (limited to 'dh_movefiles.1')
| -rw-r--r-- | dh_movefiles.1 | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/dh_movefiles.1 b/dh_movefiles.1 index f27b36f6..a2298605 100644 --- a/dh_movefiles.1 +++ b/dh_movefiles.1 @@ -39,6 +39,14 @@ Lists files to move. The filenames listed should be relative to debian/tmp/. You can also list directory names, and the whole directory will be moved. You can even use wildcards if you like. It is an error to list files here unless you use -p, -i, or -a to tell dh_movefiles which subpackage to put them in. +.SH NOTES +Note that files are always moved out of debian/tmp by default (even if you +have instructed debhelper to use a compatability level higher than one, +which does not otherwise use debian/tmp for anything at all). The idea +behind this is that the package that is being built can be told to install +into debian/tmp, and then files can be moved by dh_movefiles from that +directory. Any files or directories that remain are ignored, and get +deleted by dh_clean later. .SH ENVIRONMENT See .BR debhelper (1) |