Re: [patch] config.status builddir awareness

[Akim Demaille]

| On Mon, Jul 10, 2000 at 07:34:18PM +0200, Akim Demaille wrote:
| : >>>>> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
| : 
| : Alexandre> On Jul 10, 2000, Akim Demaille <[EMAIL PROTECTED]> wrote:
| : >> elif test -f "$ac_given_srcdir/$f"; then
| : 
| : Alexandre> This shouldn't be done when $f is a full pathname.
| : 
| : Well:
| : 
| : +     for f in $ac_file_in; do
| : +       case $f in
| : +       -) echo $tmp/stdin ;;
| : +       *) if test -f "$f"; then
| : +            # Build tree or absolute
| : +            echo $f
| : 
| : This one should be triggered first for full path names.  Or am I
| : missing something?
| 
| Shouldn't you do it like this?
| 
|        case $f in
|        -)
|          echo $tmp/stdin ;;
|        [abspath-regexp])
|          echo $f ;;
|        *)
|          <the way it was> ;;
|        esac

I don't think we need to: test -f itself will do the right thing,
whether the file is relative to build dir, or absolute wrt build dir
(i.e., just absolute), no matter what absolute means for the system.
We no longer have to test for absoluteness.