HI, On Mon, Jun 27, 2011 at 11:10:24AM +0800, Aron Xu wrote: > Package: im-config > Severity: wishlist > > I am the maintainer of fcitx related packages, and planning to switch > to im-config from im-switch.
Good. > The upcoming upstream release of fcitx > will have fbterm support, and fcitx itself will be highly modularized > hence itself won't depend on any X or gtk packages. But im-config > depends on zenity, which depends on X and libgtk, will force fcitx > pulling in those dependencies if I replace im-switch with it, this > would be unacceptable for those people who only use fcitx-fbterm. Actually, this was bug on my part. I meant to do: Depends: zenity | dialog, ${misc:Depends} If one of it exist, this program work as configuration tool. If it finds zenity, it uses zenity over dialog. > There are two ideal ways to resolve the problem: > 1.downgrade zenity to Recommends, this is the easiest way > 2.provide two packages from im-config, one depends only on dialog, > another depends on zenity. But I do not understand "fcitx itself will be highly modularized hence itself won't depend on any X or gtk packages." You do not need to use "DEPENDS" for im-config. Just "Recommends" is good enough. People may configure any way they wish to start it. Thus this recommends should come from something like fcitx-x. So installing fcitx-fbterm only should not pull in even as recommend. Please note, script hook of im-config / im-switch is in X start up code. Since I do not know how stadard start up code should be for fbterm, I can not extend im-config to support fbterm. Any suggestion is welcome. See code at: Vcs-Git: git://git.debian.org/git/collab-maint/im-config.git Vcs-browser: http://git.debian.org/?p=collab-maint/im-config.git Anyway, how soon I should fix this? Osamu > -- > Regards, > Aron Xu > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org