On Thu, Jul 06, 2000 at 06:47:50PM +0200, Akim Demaille wrote:
: | Well, what's not indentation fixes is mostly ifelse alternations without
: | any "original work", so I think the patch only counts for the extra
: | case/esac lines...
:
: But I still want an alexandreward opinion anyway :)
You are so dependwards to Alexandre... You need to become more
independwards...
: | That is incorrect use, and will therefore fail, and the person who wrote
: | that would get what's coming to him...
:
: Do you really want to make it incorrect? After all, why should it be
: forbidden, almost nothing is needed to support this.
You're right.
: Actually, why do you want stdin at all, we lived so long without...
I have a config header that originates from a common code module,
and all the files in the common code needs to get some @keywords@
replaced. This is two steps, so I need config.status applied on
the file twice. Anyways, config.status does only handle taking
file input from $srcdir so earlier I moved the temporary file back
to the top_srcdir and ran the second pass from that temporary file.
Needless to say, this only works when the source hierarchy is on
read-write media. Choosing between supporting stdin/stdout and
making config.status inputwards $builddir-aware, I chose to go for
the first solution.
Lars J
