[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ensure that generated files are read-only
From: |
Jim Meyering |
Subject: |
Re: ensure that generated files are read-only |
Date: |
Thu, 07 Sep 2006 21:06:11 +0200 |
Bruce Korb <address@hidden> wrote:
> Bruno Haible wrote:
>> Jim Meyering wrote:
>>
>>>I learned long enough ago that
>>>files like Makefile, Makefile.in, configure, etc. are generated,
>>>so that their being writable isn't a big deal. But still, for
>>>novices, ...
>> Would it help you if we consequently mark every generated file
>> (except
>> generated doc - info, html, pdf, ps) with
>> DO NOT EDIT! GENERATED AUTOMATICALLY!
>> in the first or second line?
>> Bruno
>
> Or maybe both of these lines :)
>
> -*- buffer-read-only: t -*- vi: set ro:
> DO NOT EDIT! GENERATED AUTOMATICALLY!
Good idea.
That's a nice compromise.
People who are motivated to modify a file in spite of
such advisory lines can always work around them.
In emacs, it's as easy as C-xC-q -- and in vi, :w!
Now, I'm thinking of changing coreutils' bootstrap script to add such
lines to the files it creates/copies, rather than making them read-only.
Thanks!
P.S. I'll join the other discussion on my recent gnulib changes soon.
I'm indisposed for another hour or so.
- Re: ensure that generated files are read-only, (continued)
- Re: ensure that generated files are read-only, Bruno Haible, 2006/09/09
- Re: ensure that generated files are read-only, Bruno Haible, 2006/09/09
- Re: ensure that generated files are read-only, Jim Meyering, 2006/09/14
- Re: ensure that generated files are read-only, Paul Eggert, 2006/09/14
- Re: ensure that generated files are read-only, Jim Meyering, 2006/09/14
- Re: ensure that generated files are read-only, Paul Eggert, 2006/09/14
- Re: ensure that generated files are read-only, Jim Meyering, 2006/09/15
Re: [bug-gnulib] ensure that generated files are read-only, Bruno Haible, 2006/09/07