Quote:
Originally Posted by twobob
Very helpful. nice bind-mounting.
I'm not 100% sure but some work was undertaken to identify addons in an effort to elide extensions from the incorrect device. Not sure what stage that made it to. Will have a glance at the commits.
Would be nice to make this (and other extensions) device specific.
|
This is a good example of a use for the (soon to be) KUAL.system registry.
When the registry itself is installed on a device, it will identify and adapt its device specific */system/*/ entries.
All we need to do is define a device specific value for a KUAL.system "fixed API" name, as in:
*/system/service/browser/{READABILITY_CSS, READABILITY_JS}
Then this button's installer will not need to know what model it is running on, it will just do something like:
Code:
CS_TARGET=$(cat `kdb $KDB_ROOT/system/service/browser/READABILITY_CSS`)
mount --bind <path to replacement> $CS_TARGET
- - and similar for other device specific names, paths, etc. - -
There is a kdb database build for both the armv6 and armv7 devices now being tested, and the 'shape' of the registry tree being decided upon.
So, until then, this button will probably have to be re-written for each specific device.