Bugzilla Bug 56809

My original complain is that the ebuild for dev-tex/latex-unicode is plain
horrible (but that is just my opinion). The frustration is partly due to the
fact that I don't know what the mainter did to prepare the package as it is.
Furthermore, in the USE=-cjk case, the makeunidef.pl script in the original
script can benefit from "--exclude cjkbg5,cjkgb,cjkjis,cjkhangul", which leads
to the exclusion and non-compilation of a few megabytes of data for the -cjk
users. At least that is what I used in my local overlay (mostly because I
didn't realise the package is already in portage).

I don't know why that choice was made, so I'd like to either hear the
justification behind it or see a new ebuild if possible. I really believe that
nobody benefits from the ebuild in its current form.

Sorry about your frustration. I put latex-unicode into Portaeg but haven't
tested much (cause I don't use Unicode for LaTeX). If you are uncomfortable
with the package and you have a better one, please submit it here. I'm not
happy with the current cjk USE flag for this package as we are moving towards
better handling for multilingual environment (bug #9988). Probably it's better
to use LINGUAS solution for the moment.  In addition to latex-unicode, there's
an open bug for cjk-latex (bug #40354) but I don't have much time to fix it.  I
planned to take some patches from SUSE (anyway, jmgolv will take care of it).  

Created an attachment (id=35358) [edit]
latex-unicode.ebuild

Well, this package is pretty useful as a part of the movement to utf8. This
way, I can write my latex files in utf8, though I haven't used it with Japanese
yet. In fact, the CJK part is pretty ugly, according to languages.ps.gz.

The message in the end of the original latex-unicode ebuild was pretty useful.
If you are to consider my ebuild, I'd recommend keeping the original message.

One problem with the ebuild, is that the file in SRC_URI is not versioned.

I now see that my ebuild ignores ${myconf}. Trivial to patch.

<        perl makeunidef.pl -t data -v --nocomments config/* || die
>        perl makeunidef.pl -t data -v --nocomments ${myconf} config/* || die

I tested your ebuild and it didn't work with Japanese.
It cannot find c40enc.def. I had tested several examples 
with my ebuild according to languages.pz when I committed.
Could you provide some tex files that your ebuild is able 
to process and Portage's isn't?

If cjk USE flag is the only thing I'll add it to the current ebuild. 

Not sure how to apologize.

I read the INSTALL and the README, which referenced an extra required file, plus compilation steps. Then I looked at your ebuild, and I saw that you've listed only one file, that the file is on a private server, and that that you don't do any of the things that are listed in the README. So I figured that you've prepared the file yourself, because the ebuild didn't do any of the "compile" steps that the README talks about.

Hence all the confusion.

About the cjk use flag: excluding cjk reduces the size of data/ from 2.2M to 782K... not really an issue for someone using latex.

Sorry again. Might as well mark this as inavlid, but I'd rather go hide under a pillow.

Actually, if you do want to include the IUSE=cjk... the source tarball seems to already be prepared with all possible encodings. I guess only the -cjk case can be prepared again:

src_compile() {
if ! use cjk ; then
 rm -f data/*
 perl makeunidef.pl -t data -v --nocomments --exclude cjkbg5,cjkgb,cjkjis,cjkhangul config/*
fi
}

Sorry fot the delay. Applied your patch to latex-unicode-20040307.ebuild.
Thanks for the suggestion.
If you find any other improvements please let me know.