>>"Santiago" == Santiago Vila <[EMAIL PROTECTED]> writes:
Santiago> Manoj Srivastava wrote:
Santiago> What I don't understand is why those .log files have to be
>> created.
>>
>> Because it helps me in debugging problems users may have with
>> my packages.
Santiago> We usually turn off debugging when we are confident that
Santiago> things work as they are expected to do. That's why we
Santiago> normally ship executables stripped.
A) My package, my decision when we are at that point.
B) We ship packages with -g turned on as well.
C) We strip packages for performance and space reasons; the
log files are not significantly large, and do not impact
the performance at all.
Santiago> The example `install' script in debian-emacs-policy does
Santiago> not create it, so the most simple way to avoid these files
Santiago> being 600 would be to not create them at all.
>>
>> This is throwing the baby out with the bath water. The simple
>> solution is the ensure the files are readable.
Santiago> Those files are normally not needed. Setting LOG=/dev/null
Santiago> and redirecting output to $LOG, even if we don't care about
Santiago> the mode, would be even more simple (and more consistent
Santiago> with our practice of not bloating the system because of
Santiago> debug issues) than keeping those files around with mode
Santiago> 644, and yet it would make debugging quite easy.
You can decide not to log for _your_ package. I certainly am
going to continue to log the compilation for mine.
manoj
--
Tell the truth or trump--but get the trick. Mark Twain, "Pudd'nhead
Wilson's Calendar"
Manoj Srivastava <[EMAIL PROTECTED]> <http://www.debian.org/%7Esrivasta/>
1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
