Re: -I not used by @verbatiminclude?

[Karl Berry]

    What do you think about a new keyword to set the path in

I'm scared.  This would be very unlike any other command.  It would also
be essentially impossible to implement directly/reliably in texinfo.tex
(there's no way to affect TEXINPUTS from within a TeX document), and
even in texi2dvi, it would mean somehow parsing the input file.  Imagine
@ifinfo
@addinclude foo
@end ifinfo
@iftex
@addinclude bar
@end iftex

This kind of stuff is already one of the most problematic parts of the
system, I don't want to make it worse.

    Or an environment variable?  TEXIINCLUDEPATH?

That seems better/more usual to me, but again, there's no way to make
texinfo.tex pay attention to it.  I guess I'd accept a patch for
makeinfo/texi2dvi, but realistically, I don't want to try to implement
it myself before pushing for another release.  (It's been too long
already.)

Overall, I guess I still wonder whether anything like this is necessary.
Keeping extra -I directories in sync does seem more like an
infrastructure issue than a Texinfo issue to me.  In some ways, adding
any Texinfo feature along these lines might complicate things more than
it solves, by bringing up questions of interaction, precedence, etc.  At
least right now the situation is relatively straightforward.

    in an objdir != srcdir build.  OTOH, I think 'make distcheck' do that,

Yes, it does.

Thanks,
k