The following commit has been merged in the master branch:
commit 9c84e1dd3eeb99943a9cdb0e16c93a8dc6d530a1
Author: Guillem Jover <[EMAIL PROTECTED]>
Date: Mon Aug 18 03:14:58 2008 +0300
man/dpkg-trigger.1: Set program names in bold
diff --git a/ChangeLog b/ChangeLog
index 8c613e8..962c883 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,9 @@
2008-08-18 Guillem Jover <[EMAIL PROTECTED]>
+ * man/dpkg-trigger.1: Mark program names in bold.
+
+2008-08-18 Guillem Jover <[EMAIL PROTECTED]>
+
* man/cleanup-info.8: Use a troff special character for the copyright
symbol.
* man/deb-substvars.5: Likewise.
diff --git a/debian/changelog b/debian/changelog
index 9a9ad8c..80e7b81 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -34,6 +34,7 @@ dpkg (1.15.0) UNRELEASED; urgency=low
* Improve comment on BUGS section in dpkg-deb.1 about lack of authentication
and checksum support in .deb files. Closes: #492052
* Use a troff special character for the copyright symbol on man pages.
+ * Mark program names in dpkg-trigger.1 in bold.
[ Raphael Hertzog ]
* Enhance dpkg-shlibdeps's error message when a library can't be found to
diff --git a/man/dpkg-trigger.1 b/man/dpkg-trigger.1
index db5d19e..1a38138 100644
--- a/man/dpkg-trigger.1
+++ b/man/dpkg-trigger.1
@@ -1,4 +1,4 @@
-.TH dpkg\-trigger 1 "2008-04-08" "Debian Project" "dpkg suite"
+.TH dpkg\-trigger 1 "2008-08-18" "Debian Project" "dpkg suite"
.SH NAME
dpkg\-trigger \- a package trigger utility
.
@@ -17,17 +17,17 @@ This can be used by maintainer scripts in complex and
conditional
situations where the file triggers, or the declarative \fBactivate\fP
triggers control file directive, are insufficiently rich. It can also
be used for testing and by system administrators (but note that the
-triggers won't actually be run by dpkg-trigger).
+triggers won't actually be run by \fBdpkg\-trigger\fP).
.PP
-Unrecognised trigger name syntaxes are an error for dpkg-trigger.
+Unrecognised trigger name syntaxes are an error for \fBdpkg\-trigger\fP.
.
.SH COMMANDS
.TP
.BR \-\-check\-supported
-Check if the running dpkg supports triggers (usually called from a postinst).
-Will exit 0 if a triggers-capable dpkg has run, or 1 with an error message
-to stderr if not. Normally, however, it is better just to activate the
-desired trigger with \fBdpkg\-trigger\fP.
+Check if the running \fBdpkg\fP supports triggers (usually called from a
+postinst). Will exit 0 if a triggers-capable \fBdpkg\fP has run, or 1 with
+an error message to stderr if not. Normally, however, it is better just to
+activate the desired trigger with \fBdpkg\-trigger\fP.
.TP
.BR \-h ", " \-\-help
Show the usage message and exit.
@@ -45,7 +45,7 @@ Change the location of the \fBdpkg\fR database. The default
location is
\fI/var/lib/dpkg\fP.
.TP
.BR \-\-by\-package=\fIpackage\fR
-Override trigger awaiter (normally set by dpkg through the
+Override trigger awaiter (normally set by \fBdpkg\fP through the
DPKG_MAINTSCRIPT_PACKAGE environment variable of the maintainer scripts,
naming the package to which the script belongs, and this will be used
by default).
--
dpkg's main repository
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
