Re: FYI: update .info files in $(srcdir) again

[Thien-Thi Nguyen]

   From: Alexandre Duret-Lutz <address@hidden>
   Date: Sun, 09 Nov 2003 12:11:53 +0100

   I'm interested to know why.  I've only heard about arguments
   against this so far.

i like to do doc coverage analysis[1].  it's slightly easier when the
grep/sed targets are always in cwd (yes i know adding ${srcdir} is no
big deal but that means i need to make sure it's properly defined or
pass that value in, etc).

also, when generating .info (or .texi or anything really), it's nice to
put those things elsewhere so that grepping source is simply grepping
source.  (yes i know: use a TAGS table....)  i always thought insistence
on placing .info files in the source tree to be somewhat misguided for
this reason, but confess lack of interest in learning the rationale.

thi


____________________
[1] sample script:
    # cov --- list documented Scheme and C elements
    #
    # Usage: cov
    
    cat > cov.sed <<EOF
    /^[*] /!d
    /^[*] Menu:$/d
    s/^[*] //g
    s/: .*//g
    / <[0-9]>$/d
    EOF
    
    spew ()
    {
        info -n "$1" -f guile.info | sed -f cov.sed
    }
    
    echo '('
    spew "Variable Index"
    spew "Procedure Index"
    spew "Type Index"
    spew "R5RS Index"
    echo ')'
    
    rm -f cov.sed
    
    # cov ends here