This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Making generated files read-only
- To: Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>
- Subject: Re: Making generated files read-only
- From: Jeffrey A Law <law at upchuck dot cygnus dot com>
- Date: Thu, 08 Apr 1999 14:49:24 -0600
- cc: egcs at egcs dot cygnus dot com, craig at jcb-sc dot com, doko at smile dot cs dot tu-berlin dot de, Mark Mitchell <mark at markmitchell dot com>
- Reply-To: law at cygnus dot com
In message <Pine.GSO.4.10.9904082226100.11227-100000@alphard.dbai.tuwien.ac.a
t>you write:
> On Thu, 18 Mar 1999, Mark Mitchell wrote:
> > One trick I use in my own packages is to make generated files
> > read-only. Then my editor screams at me if I try to edit them, even
> > if I don't remember to read the "MACHINE GENERATED: DO NOT EDIT"
> > comment at the top. CVS doesn't really support this, I don't think,
> > but we could have `contrib/egcs_update' mark generated files read-only
> > since it already knows which ones they are.
>
> Craig, Jeff, what do you think about this idea?
>
> If it's okay with you, I'll add that to contrib/egcs_update.
What happens to the code that wants to update those readonly files. ie,
automake, autogen and friends. If they all continue to work, then great,
if not, then making them readonly is a lose.
jeff