Hello. On Sat, 2008-12-13 at 23:12, digger vermont wrote: > > Use individual rules files in a /etc/freesmartphone/oevents/rules.d > directory rather than a monolithic rules file. > > The included patch first parses the rules.yaml file and then any files > it finds in rules.d. The patch has been tested with a button-aux.yaml > file. The patch does not create a rules.d directory.
OK, great so far. > This would allow update-alternatives to select rules files. For example: > Do I want fso-control or paroli to be launched from the AUX button? It starts to get complicated here. Next to handle the u-a we also have to take to keep changes from the user. > This works as is however it could be expanded to other possibilities. > Similar to apache2 (at least in Debian type systems) there could be > rules-available and rules-enabled directories. Utilities similar to > a2enmod and a2dismod could be written or perhaps even a GUI. I was always a bit confused by this, but it has it's benefits. > I imagine if there is a rules.d directory there would also need to be a > standard for what those files would be, such as button-aux.yaml and > button-power.yaml. Some rules files are harder to define. There could > certainly be multiple rules for incoming calls and sms. > > Perhaps is worth some discussion? I think the flexibility is worth the effort. I also think that a collection of use-cases may be good here to see what people would like to realize with the rules files. regards Stefan Schmidt
signature.asc
Description: Digital signature
_______________________________________________ smartphones-standards mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-standards
