|author||joey <joey>||2000-10-28 06:13:50 +0000|
|committer||joey <joey>||2000-10-28 06:13:50 +0000|
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
2 files changed, 18 insertions, 0 deletions
diff --git a/debian/changelog b/debian/changelog
index 633263e..546e3fe 100644
@@ -1,3 +1,13 @@
+debhelper (2.1.17) unstable; urgency=low
+ * 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
+ -- Joey Hess <email@example.com> Fri, 27 Oct 2000 23:07:42 -0700
debhelper (2.1.16) unstable; urgency=low
* dh_movefiles: fixed a regexp quoting problem with --sourcedir.
diff --git a/dh_movefiles.1 b/dh_movefiles.1
index f27b36f..a229860 100644
@@ -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.
+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.
.BR debhelper (1)