[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ensure that generated files are read-only
From: |
Bruce Korb |
Subject: |
Re: ensure that generated files are read-only |
Date: |
Thu, 07 Sep 2006 07:00:32 -0700 |
User-agent: |
Mozilla Thunderbird 1.0.7 (X11/20050923) |
Jim Meyering wrote:
> Considering the numerous uses of sed and echo (in place of cp)
> I preferred to be consistent. But I agree that it'd be better
> not to pollute the build output with output that is 99% irrelevant.
> So, how about prefixing each new line with "@", so make doesn't print them.
> E.g.,
>
> sys/select.h:
> test -d sys || mkdir sys
> @rm -f address@hidden $@
> echo '#include <sys/socket.h>' >address@hidden
> @chmod a-w address@hidden
> mv address@hidden $@
My very strong preference is to not hide commands. Disk space
(log files) is cheap. I can filter out chaff much more easily
than I can reconstruct commands that are not in the log.
No hidden commands without a good reason for hiding the command.
Please. :) Cheers - Bruce
- ensure that generated files are read-only, Jim Meyering, 2006/09/06
- Re: ensure that generated files are read-only, Paul Eggert, 2006/09/06
- Re: ensure that generated files are read-only, Paul Eggert, 2006/09/07
- Re: ensure that generated files are read-only, Paul Eggert, 2006/09/07
- Re: ensure that generated files are read-only, Ralf Wildenhues, 2006/09/07
- Re: ensure that generated files are read-only, Paul Eggert, 2006/09/07
- Re: [bug-gnulib] ensure that generated files are read-only, Bruno Haible, 2006/09/07
Re: ensure that generated files are read-only, Jim Meyering, 2006/09/08
Re: [bug-gnulib] ensure that generated files are read-only, Bruno Haible, 2006/09/07