Raphaël Hertzog wrote: > it would be nice to be able to enable a dh addon without modifying the > source package. Given this I think the best way is to have an environment > variable where you can list supplementary addons to enable. > > I can think of multiple usages in various contexts (mainly in the context > of derivatives distribution / downstream users of our packaging): > - add the dh_buildinfo call because you really want the build information > for as many packages as possible for debugging purposes > - add an addon to strip data (think documentation for an embedded > distribution) > - add an addon to extract data from the packages during build (think > ddebs)
I wonder if dealing with this in dh is the best place. For each of the above examples, it will only solve things for the 20% (or whatever it is now) of packages that use dh. OTOH, putting a wrapper about dpkg-deb will affect 100% of packages. And all your examples seem amenable to being run at dpkg-deb --build time. I'm not sure if data gathering and binary package tree tweaks are all the use cases that make sense, or just happen to be the sort you thought up. Of course, dh_builddeb *is* a wrapper around dpkg-deb that 99% of packages use. So maybe the hook would best go there. Or maybe it would make sense to build it directly into dpkg-builddeb? -- see shy jo
signature.asc
Description: Digital signature
