Hi Digger! I cc:ed Benedikt Bär since he was involved in the previous discussion on the smartphones-standards mailing list:
http://lists.linuxtogo.org/pipermail/smartphones-standards/2008-October/000644.html On Sun, 02 Nov 2008 00:50:28 +0100, digger vermont wrote: > On Sat, 2008-11-01 at 21:54 +0100, Luca Capello wrote: >> Since Debian by default would like to ship what the FSO image ships [3], >> the solution can be: >> >> 1) strictly follow upstream (i.e. FSO) solution >> >> 2) something similar to the fso-sounds-* packages, i.e. button-*.yaml >> are managed through update-alternatives and then fso-config-$DEVICE >> and fso-control can both provide an alternative >> >> 3) fso-config-$DEVICE does not provide any button configuration and >> anyone installing fso-control must configure frameworkd > > Seems like the desired solution would be one that is also > distribution-agnostic. Fully ACK, forget everything I wrote before :-) We should really push for an upstream tool to modify the rules. I was thinking about 'frameworkd-rules': ===== FSO frameworkd rules manager ---------------------------- Usage: frameworkd-rules command [rule] [value] Commands: check check if rule exists and it is activated list list the specified rule or all with no rule name get get the value for rule set set the value for rule ===== What does upstream think about this matter? Thx, bye, Gismo / Luca
pgpR6JfsGRS9W.pgp
Description: PGP signature
_______________________________________________ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
