Paul Eggert wrote:
> Here's another thought: how about this even-shorter version instead?
>
> alloca.h: alloca_.h
> $(LN_F_S) $(srcdir)/alloca_.h $@
>
> where $(LN_FS) expands to "ln -fs" in the typical case, or to
> "rm -f $@ && cp" on hosts where "ln -fs" doesn't work (e.g., Solaris 9
> a
Bruce Korb wrote:
> Or maybe both of these lines :)
>
>-*- buffer-read-only: t -*- vi: set ro:
>DO NOT EDIT! GENERATED AUTOMATICALLY!
For the user who wants to do small developments, such as tweaks in a
Makefile or config.h, and who happens to use emacs or vi, this is still
a nuisance. (L
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
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,
Jim Meyering wrote:
> I've always taken the stand that
> generated files should be read-only, and this is just another
> reason to follow that policy.
I'm vehemently opposed to such a change. On the contrary, I think the
policy should be that in a distrib tarball, _all_ files and directories
shoul
