Created attachment 316961 [details] fcitx-sunpinyin-0.3.7 ebuild The current version of app-i18n/fcitx-sunpinyin in tree is 0.2.1, which depends on =app-i18n/fcitx-4.0.1 which is OUTDATED. This results in warnings every time a world upgrade is done, and in my case the inability to upgrade glib. Attached are the version-bumped ebuild and the corresponding sunpinyin-9999 ebuild, which is required to get sunpinyin-2.0.4 in place.
Created attachment 316963 [details] sunpinyin-9999 ebuild for the (still unreleased) sunpinyin 2.0.4
oh well... mislabeled sunpinyin-9999.ebuild's mimetype, it is just another plain old ebuild script. sigh
These two ebuilds are provided in gentoo-zh overlay. You can add gentoo-zh in layman to use them. Although I am also happy to see the ebuilds landed into the portage tree, it seems that there are few live ebuild in portage tree.
Is there a version that doesn't depend on unreleased sunpinyin? I'd be happy to add more fcitx stuff to the portage tree, and keep it up to date, but we can't depend on live ebuilds. In the worst-case scenario we would make a snapshot.
(In reply to comment #4) > Is there a version that doesn't depend on unreleased sunpinyin? The latest version is fcitx-4.0.1, which is why I kept it in the main tree. > > I'd be happy to add more fcitx stuff to the portage tree, and keep it up to > date, but we can't depend on live ebuilds. In the worst-case scenario we > would make a snapshot. I have been waiting for sunpinyin-2.0.4 for about a year and don't see it coming. A snapshot might be a good solution for now.
(In reply to comment #5) > (In reply to comment #4) > > Is there a version that doesn't depend on unreleased sunpinyin? > > The latest version is fcitx-4.0.1, which is why I kept it in the main tree. > > > > > I'd be happy to add more fcitx stuff to the portage tree, and keep it up to > > date, but we can't depend on live ebuilds. In the worst-case scenario we > > would make a snapshot. > > I have been waiting for sunpinyin-2.0.4 for about a year and don't see it > coming. A snapshot might be a good solution for now. I have been using the live version since I opened this bug, and so can show that the current tip is in a reasonably good condition, at least could be considered as something ~amd64. Maybe doing snapshot is just fine if upstream is unreachable or is unwilling to do an official release. But here is an annoying bug in fcitx: inside frontend/xim/xim{handler,queue}.c there are lines of debug code that were never disabled, that causes a LOT of debug messages to show up on the tty you did "startx"; or worse, the messages make it into ~/.xsession-errors, in which case my /home partition got eventually filled up. I will soon attach a patch to correct this.
(In reply to comment #6) > But here is an annoying bug in fcitx: inside > frontend/xim/xim{handler,queue}.c there are lines of debug code that were > never disabled, that causes a LOT of debug messages to show up on the tty > you did "startx"; or worse, the messages make it into ~/.xsession-errors, in > which case my /home partition got eventually filled up. I will soon attach a > patch to correct this. A new bug has been filed for this: #427070.
(In reply to comment #5) > > I have been waiting for sunpinyin-2.0.4 for about a year and don't see it > coming. A snapshot might be a good solution for now. I strongly suggest that we do a snapshot and make an ebuild like sunpinyin-2.0.4_pre20130129 so that we can have the new fcitx-sunpinyin in portage tree and drop the outdated fcitx package.
snapshot would make sense. qiao, ben what's your idea here? anyone poked upstream?is there any chance that they can release 2.0.4? or suggest a sanity tag?
app-i18n/fcitx-sunpinyin-0.4.0 pushed, which works with the new snapshot + 31 Jan 2013; Ben de Groot <yngwin@gentoo.org> +fcitx-sunpinyin-0.4.0.ebuild, + +files/fcitx-sunpinyin-0.4.0-gcc46-compatible.patch: + Version bump, bug #454491. Thanks to Dennis Lan and Wang Jiajun for + contributions.
