Bugzilla Bug 33123

Yesterday the developer of im-ja has announced xim support
for non-GTK-applications. This being great in itself, he
unfortunately hasn't changed the version number, meaning 
the old tarball named im-ja-0.8.tar.gz is not the same as 
the one residing at the ebuild's SRC_URI now.

Can you show exactly the SRC_URI where we can get the sourcetarball? I've
just fetched im-ja from http://im-ja.sourceforge.net/im-ja-0.8.tar.gzbut
it has the same MD5 as in /usr/portage/app-i18n/im-ja/files/digest-im-ja-0.8.

Of course. The new tarball is here:
http://siliconium.net/~boti/im-ja/im-ja-0.8.tar.gz


Check http://www.tlug.jp/ML/0311/msg00056.html for the 
announcement and a few details on what B0Ti did. ID & 
password for the mailing list archive are:
http://www.tlug.jp/images/tlug-pword.png.

yakina, what do you think about making an ebuild with a different
name, say, im-ja-0.9_alpha20031109.ebuild ?

Coincidentally, this is what the author implicitly seems to 
recommend. :) Quoting http://www.tlug.jp/ML/0311/msg00061.html:

"The official v0.8 release (from September) available from SF 
doesn't have any xim support, I was just too lazy to bump the 
version number for this preview release  to 0.9-alpha. I'd want 
to wait pushing this into portage until it's released as 0.9."

Sorry to have started this unnecessary precipitation...

I've just included it as im-ja-0.9_alpha20031109.ebuild.  It is masked
until the next 0.9 release, so if you are interested in trying it,
unmask it using /etc/portage/package.unmask and then emerge.
Thanks for reporting.