Hi, Am 08.04.2017 um 05:05 schrieb Guillem Jover: > On Fri, 2017-03-17 at 16:31:27 +0100, Markus Koschany wrote: [...]
To me there seems to be some confusion which package should document the information which I have requested in this bug report. In have no strong preferences whatsoever but it should be documented somehow. At the moment the man page of dpkg-maintscript-helper appears to be the only source of information how to handle the four use cases of (rm_conffile, mv_conffile, symlink_to_dir and dir_to_symlink). Aside from man dh_installdeb I couldn't find any information in debhelper about *.maintscript files and how to use them correctly. If debhelper is the correct place to document this, then please reassign to debhelper. Though at least I would expect a link or pointer to the additional documentation in man dpkg-maintscript-helper. >> It should be more obvious why the package argument is >> needed at all when you have to create one $PACKAGE.maintscript file per >> package anyway. > > This is rather confused, and has nothing to do with how > dpkg-maintscript-helper operates, but rather how debhelper uses its > files and how it might or might not add the package arguments on its > own. Exactly it is confusing and thus my bug report. According to /usr/share/debhelper/autoscripts/maintscript-helper debhelper just calls dpkg-maintscript-helper with the arguments provided in its maintscript files. For me dpkg and debhelper are just two sides of the same coin. >> Please also clarify that [package] does not imply that a single maintscript >> file will act on the binary[package]. > > I'm no sure what you mean here exactly, but this seems to me it's > something for debhelper to document if at all. You need one maintscript file per binary package. I thought I could get away with one maintscript file and use it like that symlink_to_dir /usr/share/doc/holotz-castle /usr/share/doc/holotz-castle-data 1.3.14-8~ holotz-castle symlink_to_dir /usr/share/doc/holotz-castle-editor /usr/share/doc/holotz-castle-data 1.3.14-8~ holotz-castle-editor I understand that maintscript files work like every other debhelper file now, but the reason what got me confused in the first place was the [package] argument and the documentation in dpkg-maintscript-helper. >> I think an example how to use dpkg-maintscript-helper with debhelper's >> maintscript files would also be appreciated. > > This would be a layer violation, I'm not planning on documenting how > upper layers are using dpkg in this way. Please get debhelper to > clarify any of this if it's not yet clear. As I said at the beginning I have no strong preferences but honestly the man page of dpkg-maintscript-helper is the best place to document use cases. At least I would appreciate it if you pointed to additional information about maintscript files because that's what a lot of maintainers actually use. Regards, Markus
signature.asc
Description: OpenPGP digital signature
