[tex-k] problems with dvips search paths....

[Andrew Komornicki]

Karl and friends, 
 
thank you for the input.  
Your response does pose the question of why was dot (.) 
removed from the search path.  Can config.foo files be that insecure??  
 
this does bring up at least two more questions: 
  
On my TexLive2008 installation I find that there is a config.ps file 
in two places: 
    ./texmf/dvips/config/config.ps 
    ./texmf-config/dvips/config/config.ps 
which one takes precedence and why ?? 

  why is it that when I type: 
    kpsewhich   config.foo    
   or 
    kpsewhich  -must-exist config.foo 
  it is not able to find it ?? 
 
I have modified the value of TEXCONFIG to include  (.) and dvips works well.  
regards,
andrew 


At 03:05 PM 8/12/2009, Karl Berry wrote:
>    Current working directory had been removed someday
>
>In TL 2003, looks to me.
>
>    from TEXCONFIG due to some reason, which I don't remember.
>
>Security paranoia, as I recall.
>
>    See the output of
>    kpsewhich -var-value=TEXCONFIG
>
>Yep, or if you really want to see the complete path with everything
>expanded, 
>kw --expand-path=\$TEXCONFIG
>(add | tr : '\n' to get each dir on its own line).
>
>    and put config.foo under a suitable subdirectory
>
>I didn't check, but I seem to recall that there's enough options around
>that it'd also be possible to add any given directory to the TEXCONFIG
>path via ~/.dvipsrc or some such.  Not sure, though.