On 30 Dec 2007 dvipdfmx was added as dependency. (refer to Bug #203039) The dependency is missing in 2008-r1. Please add the dependency again. At the moment no ebuild of texlive-2008 depends on it so correct multi-byte character support with use xetex is broken.
got any real example of something failing? because tl-xetex-2007 has *x*dvipdfmx dep which is now in tl-core so we don't need it for 2008...
ok, i see that xdvipdfmx is available on my system. the problem actually was kile-2.0.2. kile's dvitopdf build setting in modern mode uses dvipdfmx by default. of course it reports a problem when dvipdfmx is not installed. i did not notice that xdvipdfmx is in tl-core now. i don't know the best way to solve this. probably kile could be patched to use xdvipdfmx by default. at least when tl is installed as latex environment which is the default at the moment.
So is Kile basically mising the dev-texlive/texlive-xetex dependency and needs to be updated to use the xdvipdfmx binary by default or is there more to it?
i don't think it is really missing the dependency. (x)dvipdfmx is an optional tool for kile to do dvi to pdf conversion. the conversion command can be set in the build preferences for dvitopdf. the default value for this setting seems to be dvitopdfmx. kiles system check utility finds a missing divtopdfmx when the dvitopdfmx package is not installed. when livetex-xetex is installed the default value still generates this error message. since xetex installs xdvitopdfmx, which supersedes dvitopdfmx, doesn't it, the user should be informed, that xdvitopdfmx is present explicitly. either by changing the default value for kile or by a message when xetex is installed or something like that. it is just my opinion that kile should not report an error when one of the possible optional tools for dvitopdf conversion is present but should use the best of the tools. it may be that this is a case for a change in the upstream package and shouldn't be fixed by gentoo.
Bernd, what definitely needs to be changed is the binary Kile is looking for by default. Regarding dependency or not, it is of course possible to simply add a post install message. Since the creation of PDF's is a very common use case and the dependency is a rather light one, I'd tend towards forcing it, instead to let the user search for what he's missing. Since it's part of texlive-core 2008 the discussion is pointless. Tex team: Has the binary in question in texlive-core 2008 the extra x at the beginning or not?
(In reply to comment #5) > Tex team: Has the binary in question in texlive-core 2008 the extra x at the > beginning or not? Yes, there is only xdvipdfmx. *dvipdfm* is somewhat in a mess: dvipdfm is found in: - app-text/dvipdfm - tetex - ptex (this means I've unbundled it from the distro for texlive) dvipdfmx is found in app-text/dvipdfmx xdvipdfmx is found in: - >=app-text/texlive-core-2008 - app-text/xdvipdfmx This means xdvipdfmx has been integrated in texlive because upstream does it that way and we don't have anymore updates of the standalone package. All of them can to dvi->pdf conversion; the major advantage of xdvipdfmx is that it also handles xetex's xdv files.
regarding aballier's comment, the depedency shouldn't be added as there is no missing functionality with texlive-core. Reopen if you disagree. Thanks
