Verbose build log
Hello, VLC 1.1.0 uses automake 1.11 and so the build can produce non-verbose logs like the kernel does for some years. CC foo.o CCLD foo.so ... We can revert to the old fully verbose behaviour if we like. Do you know if there is a Debian or pkg-multimedia policy/best-practice on this matter. Verbose log can help debug FTBFS but increase the size of the log by 2 or 3 order of magnitude Regards -- Xtophe ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Re: Verbose build log
On Thu, Jun 10, 2010 at 10:12, Christophe Mutricy xto...@chewa.net wrote: Hello, VLC 1.1.0 uses automake 1.11 and so the build can produce non-verbose logs like the kernel does for some years. CC foo.o CCLD foo.so ... We can revert to the old fully verbose behaviour if we like. Do you know if there is a Debian or pkg-multimedia policy/best-practice on this matter. Verbose log can help debug FTBFS but increase the size of the log by 2 or 3 order of magnitude I would think the time you waste by waiting a 3Mb file to download instead of a 3Kb file is more than regained by the detailed command lines which could provide help with problematic flags. It's still your call, though. I don't believe there is any policy on this matter. -- Saludos, Felipe Sateler ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Re: Verbose build log
On Thu, Jun 10, 2010 at 02:15:05PM -0400, Felipe Sateler wrote: On Thu, Jun 10, 2010 at 10:12, Christophe Mutricy xto...@chewa.net wrote: Hello, VLC 1.1.0 uses automake 1.11 and so the build can produce non-verbose logs like the kernel does for some years. CC foo.o CCLD foo.so ... We can revert to the old fully verbose behaviour if we like. Do you know if there is a Debian or pkg-multimedia policy/best-practice on this matter. Verbose log can help debug FTBFS but increase the size of the log by 2 or 3 order of magnitude I would think the time you waste by waiting a 3Mb file to download instead of a 3Kb file is more than regained by the detailed command lines which could provide help with problematic flags. It's still your call, though. I don't believe there is any policy on this matter. Debian Policy is based on common practices, not the other way around. I guess you are right, Felipe, that this is not governed by policy, but only because not yet written: I do believe it is a common practice to avoid build noise silencers. Here's one small piece of the puzzle: http://bugs.debian.org/551453 You can probably find some debates with varying viewpoints by searching debian-de...@lists.debian.org if not convinced as easy as I was :-) Kind regards, - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: Digital signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Re: Verbose build log
On Thu, Jun 10, 2010, Christophe Mutricy wrote: We can revert to the old fully verbose behaviour if we like. Do you know if there is a Debian or pkg-multimedia policy/best-practice on this matter. Verbose log can help debug FTBFS but increase the size of the log by 2 or 3 order of magnitude I understand the best practice is to use verbose build logs for package builds so that we can still grep them for flags and the like. -- Loïc Minier ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
