View Single Post
Old 10-05-2016, 08:32 AM   #258
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by nasser View Post
Instead of an update_*.bin, we could also have a "install" script. This would check the dpi and extract the appropriate image files. But again, won't be as user friendly as just extracting the kterm folder into /mnt/us/extensions.
- - - -
It would be the same script, regardless of how called.
By within the processing of the update package or by user action.

@baf: I do not follow why it would be required to install files that do not match the devices dpi.
knc1 is offline   Reply With Quote