Primary reason why I raised it appeared when I tried hackable1 Debian-based distribution for freerunner. X server was hardcoded to use /usr/bin/xkbd for a keyboard which comes up whenever user presses AUX button. There were no easy way to alternate the input method. So for qwo package I just suggested to symlink xkbd -> qwo. Having alternates for it would have resolved the problem.
since in this case custom x-server is relying on its presence, depends on x-keyboard should be for that custom package of X. and since it is X which takes care about raising the keyboard, it should be ok even for login screens (although on the phones usually it is a single-user environment, so no need for login/session management per se) On Thu, 12 Mar 2009, Goswin von Brederlow wrote: > Neil Williams <codeh...@debian.org> writes: > > However, there is another issue here - if the device is multi-user, > > most login managers cannot cope with a touchscreen keyboard. gpe-login > > is one that can, gdm cannot. > > Having touchscreen keyboard support in X is good as long as the user > > can log into their X environment first. > > ;-) > Recommends/Suggests? > That would hint to having a meta package instead of a virtual one. > MfG > Goswin -- Yaroslav Halchenko Research Assistant, Psychology Department, Rutgers-Newark Student Ph.D. @ CS Dept. NJIT Office: (973) 353-1412 | FWD: 82823 | Fax: (973) 353-1171 101 Warren Str, Smith Hall, Rm 4-105, Newark NJ 07102 WWW: http://www.linkedin.com/in/yarik -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org