Inline replied below: 2011/12/18 Osamu Aoki <os...@debian.org>: > I do not understand "some arguments happened". Who was involved? > gcin upstream? HIME upstream, QA team, previous gcin maintainer?
I have mistaken "O" as "Obsoleted" (actually, Orphaned), and the argument from gcin upstream arised with HIME upstream over the "Obsolescence" since that ITP bug. To apologize with gcin and HIME upstreams, I decided to maintain HIME myself. (It made me begin using HIME) I wish someone else could take care of gcin recently. Kanru (gcin ex-maintainer) posted that gcin is maintained by debian-pkg-ime just now, and he is looking for co-maintainer. > I did not even realize "Hime (姫) is the Japanese word for princess." > It is unfortunate result of GTK decision to use the same environment > variable to enable GTK immdule for GTK2 and GTK3. If they had chosen > the similar choice like Qt4, I did not need to do this. > > If one exists but not the other one, then you enable GTK immdule > without supporting immdule. Since we do not expect GTK2 apps to be > purged for wheezy (unlike Qt3), I should not create situation with > likely breakage. People can override it by manual configuration > but default should serve most people without much tweaking. Whoever > install these system, the added space for additional package is small. > We are talking desktop even for LXDE. In this case, should I pack gtk2 immodule with gtk3 immodule together, or putting hime-gtk3-immodule into Recommend is enough? > I am rephrasing these now. So I will make it consistent. Thank you. > One big question is the order of these IMs. > > Currently > 20 ibus > 22 fcitx > 24 uim > 48 scim missing Qt4 support etc. (Well there is via bridge ...) > 50 gcin it was Chinese only but now I know it has some anthy usage. > ... > > If gcin maintainer asks with explanation, I think I need to move gcin > between uim and scim. > > Question is where should HIME should go in this order. > > (I am thinking 26, it is still new but there is someone caring it. gcin > should be 28 if new maintainer asks.) I have no idea either. This may raise another argument. > As for your ITP, package description needs to be revised. This is > substandard. You have to provide proper short and long description. > > http://www.debian.org/doc/manuals/developers-reference/best-pkging-practices#bpp-desc-basics > “If you are having problems writing your description, you may wish to > send it along to <debian-l10n-engl...@lists.debian.org> and request > feedback.” > > Also, you need to explain upstream situation and difference to me > separately so I have better understandings. > OK. I will take care of package descriptions. And, I put this package into collab-maint here: http://anonscm.debian.org/gitweb/?p=collab-maint/hime.git;a=summary (I should put it to #652022) The “argument” situation is described in the above in-line reply. > Once you finish all these, let me know. I will update package. Thank you a lot, -- Yao Wei -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
