dh_* commands.
To help you get started, I've included an example of a debian/rules file
-that uses debhelper commands extensivly. See
+that uses debhelper commands extensively. See
/usr/doc/debhelper/examples/rules . These files are also useful as they give
one good order you can run the different debhelper scripts in (though other
variations are possible).
Converting from debstd to debhelper:
-----------------------------------
-Debhelper is designed to be mostly backwards compatable to debstd. I say
-mostly becuase I haven't made debhelper handle everything that debstd does
+Debhelper is designed to be mostly backwards compatible to debstd. I say
+mostly because I haven't made debhelper handle everything that debstd does
yet, and in a few cases, it does things differently (and I hope, better).
In general, you can switch over to using debhelper as follows. In your
programs. The upstream changelog is passed to dh_installchangelogs, and the
docs are passed to dh_installdocs.
-Debstd has many switches, that turn off differnt parts of it. So if you
+Debstd has many switches, that turn off different parts of it. So if you
were using debstd -m to tell it not to automatically install manpages,
for example, you can just comment out the dh_installmanpages line.
Finally, debstd automatically modified postinst, postrm, etc scripts. Some
-of the dehelper apps do that too, but they do it differnently. Debstd just
-appends its commands to the end of the script. Debhelper reqyires that you
+of the dehelper apps do that too, but they do it differently. Debstd just
+appends its commands to the end of the script. Debhelper requires that you
insert a tag into your scripts, that will tell debhelper where to insert
commands. So if you have postinst, postrm, etc scripts, add a line reading
-"#DEBHELPER" to the end of them.
+"#DEBHELPER#" to the end of them.
Once you think it's all set up properly, do a test build of your package. If
-it works ok, I reccommend that you compare the new package and the old
+it works ok, I recommend that you compare the new package and the old
debstd-generated package very closely. Pay special attention to the postint,
postrm, etc scripts.
binary-arch debian/rules target, and the architecture independent packages
in the binary-indep debian/rules target.
-To faciliatate this, as well as give you more control over which packages
+To facilitate this, as well as give you more control over which packages
are acted on by debhelper programs, all debhelper programs accept the
following parameters:
additional package.
Sometimes, you might want to use some other temporary directory. This is
-supported by the -P flag. The direcotry to use is specified after -P, for
+supported by the -P flag. The directory to use is specified after -P, for
example, "dh_installdocs -Pdebian/tmp", will use debian/tmp as the temporary
directory. Note that if you use -P, the debhelper programs can only be
acting on a single package at a time. So if you have a package that builds
+debhelper (0.27) unstable; urgency=low
+
+ * README: fixed typoes (one serious).
+ * Ran ispell on all the documentation.
+
+ -- Joey Hess <joeyh@master.debian.org> Sun, 30 Nov 1997 18:48:20 -0500
+
debhelper (0.26) unstable; urgency=low
* dh_installdirs: Do not create usr/doc/$PACKAGE directory. Bug #15498
and
.B \-p
arguments are cumulative. If none are specified, then all packages listed in
-the control file will have thier package build directories cleaned up.
+the control file will have their package build directories cleaned up.
.SH ENVIRONMENT
.TP
.I DH_VERBOSE
.SH "DESCRIPTION"
dh_du is a debhelper program that is responsible for generating
a DEBIAN/du file, which lists the disk usage of directories in the package.
-This file isn't used by anthing yet, but it could be helpful for a future
+This file isn't used by anything yet, but it could be helpful for a future
debian installer program.
.P
The du file is installed with proper permissions and ownerships.
and
.B \-p
arguments are cumulative. If none are specified, then all packages listed in
-the control file will have thier permissions fixed.
+the control file will have their permissions fixed.
.SH ENVIRONMENT
.TP
.I DH_VERBOSE
arguments are cumulative. If none are specified, then all packages listed in
the control file will be effected.
.P
-Note that dh_installdocs will happily copy entire directory hiearchies if
+Note that dh_installdocs will happily copy entire directory hierarchies if
you ask it to (it uses cp -a internally). If it is asked to install a
directory, it will install the complete contents of the directory.
.SH ENVIRONMENT
that package.
.P
A file named debian/examples (for the first binary package in debian/control),
-or debian/package.exmaples (for each additional package in debian/control) can
+or debian/package.examples (for each additional package in debian/control) can
list other files to be installed.
.SH OPTIONS
.TP
arguments are cumulative. If none are specified, then all packages listed in
the control file will be effected.
.P
-Note that dh_examples will happily copy entire directory hiearchies if
+Note that dh_examples will happily copy entire directory hierarchies if
you ask it to (it uses cp -a internally). If it is asked to install a
directory, it will install the complete contents of the directory.
.SH ENVIRONMENT
filenames that look like man pages. It uses
.BR file (1)
to verify that the files are in the correct format. Then, based on the
-files' extentions, it installs them into the correct man directory.
+files' extensions, it installs them into the correct man directory.
.P
All filenames specified as parameters will be skipped by dh_installmanpages.
This is useful if by default it installs some man pages that you do not want
.SH "SEE ALSO"
.BR /usr/doc/debhelper/README
.SH BUGS
-Man pages with the extention
+Man pages with the extension
.B .man
are not automatically installed.
.P
.SH "SEE ALSO"
.BR /usr/doc/debhelper/README
.SH BUGS
-There is no guarentee that the program will get the shlibs file right. For
+There is no guarantee that the program will get the shlibs file right. For
example, it may not correctly guess the major number of your package. In
-casews like these (and perhaps in general, just to be safe), it is better to
+cases like these (and perhaps in general, just to be safe), it is better to
create a debian/shlibs file by hand.
This is a "do what I Mean" type program - you have been warned!
.SH AUTHOR
.P
Note that this package modifies your postinst and postrm files. See
.BR dh_installdebfiles (1)
-for an explination of how this works.
+for an explanation of how this works.
.SH OPTIONS
.TP
.B \-v
This currently has no effect.
.TP
.B file ...
-Test for the existance of these files.
+Test for the existence of these files.
.SH ENVIRONMENT
.TP
.I DH_VERBOSE
The program takes a list of man pages that should be symlinked to
.BR undocumented (7)
It determines what directory the man pages should be placed in by examining
-their extentions - pages ending in "x" go into /usr/X11R6/man/, while pages
+their extensions - pages ending in "x" go into /usr/X11R6/man/, while pages
that end in anything else go in /usr/man/. It also examines the extention to
see what section the man page belongs in. After figuring this out, it
generates the necessary symlinks to