kmaps on PPI

[JoXo009]

I'm not sure if it's a bug.

When installing the kmaps.tce extension into a PPR* TC and adding the loadkmap < /usr/share/kmap/de-latin1.kmap
line to the /opt/bootlocal.sh file
everything works fine. After restart the German keymap is active.

When doing the same into a PPI** TC installation after restart the default US keymap is active and all the keymap files in the
/usr/share/kmap/-folder
are gone.

Naturally there is a workaround. After installing the kemap.tce extension into a PPI TC and before shutting down you can copy the whole folder
/usr/shere/kmap/*
to a persistent place (home directory or hdd) and change the entry in the
/opt/bootlocal.sh file appropriately.

But I doubt if such workaround is the expected behaviour of that extension.

So maybe it's a bug.

-------
*  PPR installation created by editing first boot with e-key to tce=hda1
    and installing the xfe file manager, who is persistent now.
**PPI installation created by editing first boot with e-key to local=hda1
    and installing the xfe file manager, who is persistent now.

[JoXo009]

I should add

When on a PPI install and not using the described workaround (copying the files to a persistent place  b e f o r e  shutting down) you run in a major problem.

After next boot all your kmaps files are gone, so you try to install them again, but that's impossible as you get the error 'already installed'.

In fact the 'already installed' link (/usr/local/tce.installed/kmaps) is in place, but with the exeption of the us.kmap all corresponding files all gone.

So you are lost and condemed to hit 'z' when you want to write 'y' for eternity.

[JoXo009]

A possible workaround for the second problem = new install impossible could be to delete the file
/usr/local/tce.installed/kmaps

After deleting that file a new install is possible again.

But this workaround would mean that you have to redownload kmaps after each start and could use the keyboard only in the usual way if you are online.

No real workaround in my eyes.

It must be possible to make the right kmap permanant in a PPI installation without remastering TC.

[roberts]

Your using a PPI which implies /usr/local/ is persistent.
However, it also means that you should use PPI compatible extensions.

keymaps.tce is not PPI compatible. It installs into /usr and not /usr/local/

Mixing PPI and non-PPI can quickly become confusing, you would have to add /usr/share/kmap to your /opt.filetool.lst and perform the backup/restore or setup and specify a tce directory to store and henceforth autoload keymaps.tce upon each boot.

Or perhaps, you can try to repackage keymaps to store in /usr/local and thus make it a PPI compatible extension, and many would benefit.