Bug#765446: [debhelper-devel] Bug#765446: debhelper build target status file packagename.debhelper.log is not documented

2014-10-15 Thread Joey Hess
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

Bug#765446: [debhelper-devel] Bug#765446: debhelper build target status file packagename.debhelper.log is not documented

2014-10-15 Thread Mikko Rapeli
On Wed, Oct 15, 2014 at 10:08:15AM -0400, Joey Hess wrote: 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

Bug#765446: [debhelper-devel] Bug#765446: debhelper build target status file packagename.debhelper.log is not documented

2014-10-15 Thread Joey Hess
Mikko Rapeli wrote: I have fought this issue for years. Build a package and then try to fix some bugs locally. Silly bugs like bad .install or package scripts should be straight forward to fix without complete rebuild of the package, which can take hours, or even days on smaller machines. If I

Bug#765446: [debhelper-devel] Bug#765446: debhelper build target status file packagename.debhelper.log is not documented

2014-10-15 Thread Mikko Rapeli
On Wed, Oct 15, 2014 at 12:41:19PM -0400, Joey Hess wrote: Mikko Rapeli wrote: I have fought this issue for years. Build a package and then try to fix some bugs locally. Silly bugs like bad .install or package scripts should be straight forward to fix without complete rebuild of the