Mikko Rapeli wrote: > debhelper build status log file is not documented in manual pages. > Common developer use cases involve modifying list of installed files > and package install scripts, and for these use cases a complete re-compile > of the packages in not necessary. Instead developers could modify > the package status log to re-execute all steps after build target, for > example.
I am not comfortable with encouraging this kind of hacking. It can result in a package getting built while the modified source doesn't build successfully, worse, has different contents when built straight through from a clean build. So a developer might engage in this kind of hacking, test the resulting binary package and see it's good, and then fire off a dpkg-buildpackage and not test that clean build, and upload a broken package. -- see shy jo
signature.asc
Description: Digital signature
