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 you already know? Anyway, I think something like the following could help. EXAMPLES if dpkg --compare-versions "$2" lt-nl 5.12.0 then dpkg-trigger --no-await perl-major-upgrade fi Informs interested packages that a major perl upgrade has occured. Packages with "interest perl-major-upgrade" in their triggers control file will have the trigger added to their pending trigger list. For each interested package foo, "foo.postinst triggered '<list>'" will be run with <list> a space-separated list including perl-major-upgrade before foo is next used to satisfy dependencies, or at the end of the dpkg run at the latest. generate_font >/usr/share/fonts/truetype/foo/bar.ttf dpkg-trigger /usr/share/fonts/truetype/foo/bar.ttf Informs interested packages about a new or updated font under /usr/share/fonts, just as if it had been unpacked as part of the package's files list. The current package will not be used to satisfy dependencies until the fontconfig cache is regenerated, so this is safe even if the font is used in the maintainer scripts of other packages. Though I doubt that second example would actually work, and I imagine that it would be possible to come up with more realistic examples if wanted. Does the trigger name have to match exactly (i.e., "/usr/share/fonts")? I assume trigger names are not allowed to contain a space character and that trigger names not based on paths conventionally do not start with a forward slash. Are there any other relevant rules or conventions? Thanks and hope that helps. Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org