Bug#633410: dpkg-trigger.1: does not explain trigger-name and command arguments

2011-07-10 Thread Raphael Hertzog
On Sat, 09 Jul 2011, Jonathan Nieder wrote: Sounds promising! Now what values can trigger-name and command have? Unfortunately the manpage does not say. There's no explicit list of value... a trigger name is just that, the name of a trigger. Can you suggest a wording that would make it

Bug#633410: dpkg-trigger.1: does not explain trigger-name and command arguments

2011-07-10 Thread Jonathan Nieder
Raphael Hertzog wrote: There's no explicit list of value... a trigger name is just that, the name of a trigger. Can you suggest a wording that would make it clearer for you because I don't see what can be improved. Have you tried reading it as though you were a new packager, forgetting what

Bug#633410: dpkg-trigger.1: does not explain trigger-name and command arguments

2011-07-10 Thread Raphael Hertzog
Hi, On Sun, 10 Jul 2011, Jonathan Nieder wrote: Raphael Hertzog wrote: There's no explicit list of value... a trigger name is just that, the name of a trigger. Can you suggest a wording that would make it clearer for you because I don't see what can be improved. Have you tried

Bug#633410: dpkg-trigger.1: does not explain trigger-name and command arguments

2011-07-09 Thread Jonathan Nieder
Package: dpkg Version: 1.16.0.3 Severity: minor Justification: documentation Files: /usr/share/man/man1/dpkg-trigger.1.gz Hi, Today I was looking to make a bug fix that would involve using dpkg-trigger in a maintainer script directly. So, to the manpage. It says: SYNOPSIS