Hi! On Tue, 2013-08-13 at 15:16:49 -0700, Russ Allbery wrote: > Joey Hess <jo...@debian.org> writes: > > Also it could save the whole log to someplace when minimizing the > > console output, to refer back to. Perhaps ../$package_$version.buildlog > > (which gets a step closer to including that in the dsc and uploading > > local build logs..) > > debuild, pbuilder, and related packages currently use > ../<package>_<version>_<arch>.build for this output. Maybe the > lower-level build architecture should take over maintaining that log file > instead and those tools should be modified to assume that's already > happening and move that log file around like the other build products?
Definitely, and planned (#476221) to be fixed pretty soon. But the problem is that this can not be enabled by default (only through an option initially, until the upper layers rely on a dpkg-buildpackage with such option and use it) because the different tools might fight over the file and might either truncate it or write duplicate data, etc. Using a different path might be an issue for builds producing huge log files. Thanks, Guillem -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130814091907.ga31...@gaara.hadrons.org
