Hi,

Removal of xkbcomp fork/exec on servert startup is quite hard task --
why not shift responsibility to client side: start server with some
predefined keymap and make running xkbcomp the responsibility of session
scripts?

This change will make xkb data completely client-side (though given
clients may connect from different hosts xkb introspection cannot be
dropped from protocol).

It should be easy enough (much easier than original task) to cover the
common configuration with X server on the same host as desktop session
and provide tool which reads xorg.conf and invokes xkbcomp.

-- 
  http://fossarchy.blogspot.com/

Attachment: pgpSAPquxjzHm.pgp
Description: PGP signature

_______________________________________________
[email protected]: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: http://lists.x.org/mailman/listinfo/xorg-devel

Reply via email to