Re: texconfig should not stop when unimportant files are missing

Reinhard Kotucha <[email protected]> schrieb:

>>>>>> "Frank" == Frank Küster <[email protected]> writes:
>
>     > texconfig is quite strict in it's checking whether files are
>     > available. We found this out because Lars had messed up his
>     > /etc/X11 directory and therefore lost /etc/X11/app-defaults/XDvi
>     > (in Debian: ls -l /usr/share/texmf/xdvi/XDvi
>     > .. /usr/share/texmf/xdvi/XDvi -> /etc/X11/app-defaults/XDvi )
>
> I removed texmf/xdvi/XDvi and both, xdvi and texconfig worked properly.
> Did you get an error message? 

And did texconfig resurrect the file? I also had this problem;

~~# mv /usr/share/texmf/xdvi/XDvi .
~~# texconfig init

and kpathsea found the file in the working directory and copied it
back... 

>     > [...] but I wouldn't be surprised if such a user does a 
>     > rm -rf /etc/X11 if he finds this directory.
>
> Use rm -rf with care.

Of course. But this is a general proposal - there are many reasons why a
file is missing or moved, and it would be nice if texconfig would be
more clever in which files it really needs. I know this is hard to
achieve (especially because all the file checks are done before the
argument list is parsed). I wouldn't rate this as a bug, but the
opposite would be a nice feature.

Regards, Frank
-- 
Kleiner Ansporn: Längeres Arbeiten mit dem Emacs zahlt sich spätestens
dann aus, wenn man vor der Herausforderung steht einen BH zu öffnen.
[Ralf Angeli in dctt]