Re: texi2dvi --clean bug

[Eli Zaretskii]

On 3 Jan 2001, Jan Nieuwenhuizen wrote:

> In LilyPond we have a number of texi documents that @include
> others:
> 
>     @include foo.texi  @c foo.texi resides in ..
> 
> and the makefile accordingly adds .. to $TEXINPUTS.

Isn't this a bug in LilyPond?  Variables that list directories shouldn't 
include relative paths.

>   # If clean mode was specified, then move to the temporary directory.
>   if test "$clean" = t; then
>     $verbose "cd $tmpdir_src"
>     cd "$tmpdir_src" || exit 1
>   fi
> 
> I guess it would be much better to just rm -f any tex-generated files?

I don't know.  It certainly sounds dangerous: you could remove files 
which this TeX run didn't generate, or which even don't belong to TeX at 
all.

I think if $TEXINPUTS is allowed to use relative file names, perhaps 
texi2dvi --clean should convert them all to absolute?