I have tetex 3.0_p1-r3 and xdvik 22.40y-r2 emerged here. However, xdvik on startup gripes that xdvi.cfg is not in the XDVIINPUTS. locate xdvi.cfg reports 3 locs: in /etc/texmf/xdvi, /var/lib/texmf/xdvi, and /usr/share/texmf/xdvi . Am I *supposed* to manually tweak XDVIINPUTS? tetex/xdvik install in debian has it set up out of the box. FWIW, I have no custom TEXMF/TEXINPUTS/XDVIINPUTS defined in my env, and never messed manually with the texmf system-wide stuff. Current use flags: [ebuild R ] app-text/xdvik-22.40y-r2 USE="-cjk -libwww" 0 kB [ebuild R ] app-text/tetex-3.0_p1-r3 USE="X doc tk -Xaw3d -lesstif -motif -neXt" 0 kB This is what xdvi prints: Xdvi Error: Could not find config file xdvi.cfg in path "" - disabling T1lib. Direct Type 1 (PostScript) font rendering has been disabled. You should try to fix this error, since direct Type 1 font rendering gives you a lot of benefits, such as: - quicker startup time, since no bitmap fonts need to be generated; - saving disk space for storing the bitmap fonts. To fix this error, check that xdvi.cfg is located somewhere in your XDVIINPUTS path. Have a look at the xdvi wrapper shell script (type "which xdvi" to locate that shell script) for the current setting of XDVIINPUTS.
If you emerged tetex with X use flag on, you already have xdvik on your system and you don't need to install xdvik by yourself. Moreover, xdvik-22.40y-r2 is intended to work with tetex-2 series, so if you really want to install xdvik by yourself, please unmask and use xdvik-22.84.x instead. I'll add block to xdvik-22.40y-r2 shortly.
Fixed. Thanks for the bug report.
