On 09/04/2014 06:18 PM, Chris Morley wrote:
> 
> Well then I wish we picked distros that had the packages we already used.
> Gscreen and gmoccapy have used Onboard for a very long time.
> 
> Since both distros are based on Debian, can we pull in Ubuntu's Onboard 
> package?

I just pushed the "Launch Keyboard" button in gscreen and i understand
what you're talking about now.  Before tonight I didn't know that
gscreen (and gmoccapy) shell out to /usr/bin/onboard.

That kind of usage of external programs is fine, but it should be noted
in the package metadata: linuxcnc.deb should Depend on onboard.deb.
That would have alerted us to this problem as soon as we tried to run on
Wheezy.

I'm now "on board" with your quest to fix this problem.  I can think of
two different ways to fix it:

Option 1: Make onboard.deb available on Wheezy, as you suggest.  This
might be as simple as copying and compiling the Ubuntu onboard package
for Wheezy, but it might be harder if that package has dependencies
which Wheezy doesn't meet.  And, more importantly, this option also
comes with the ongoing maintenance task of keeping our fork of the
onboard package up-to-date, and carrying it forward to future distros we
want to support.

Option 2: Find an on-screen keyboard that's already packaged for Wheezy
and teach gscreen (and gmoccapy) to look for both and use whichever one
it finds.  A quick look at the Wheezy package list turns up the
following packages which look like they provide on-screen keyboards (i
haven't tried any of them): caribou, florence, kvkbd, literki,
matchbox-keyboard, and xvkbd.

I prefer option 2 because it's a one-time effort, and it keeps up with
the changing software ecosystem we exist in.


-- 
Sebastian Kuzminsky

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Reply via email to