[pkg-fso-maint] opreferences rules (was Re: Some debian questions)

[Luca Capello]

Hi there!

Please continue this discussion on the smartphones-standards mailing
list [1], I think it belongs there and I set R-T and M-F-T accordingly.

On Wed, 29 Oct 2008 04:21:01 +0100, Guillaume Chereau wrote:
> On Wed, 2008-10-29 at 10:29 +0800, Guillaume Chereau wrote:
>> On Tue, 2008-10-28 at 14:51 +0100, Benedikt Bär wrote:
>> > I am currently setting up a debian system on my FreeRunner, but I have
>> > some questions. :)

The Debian FSO Team [2] mainly uses the smartphones-* mailing lists [1]
for discussions, please direct your questions there whenever you develop
on Debian and/or for Debian.

>> > 1) I'm writing some python programs to interact with the FSO framework.
>> > I have seen there's now support for a "rules" file, which seems quite a
>> > nice idea.
>> > 
>> > Now, I would like to be able to modify these rules via my program. That
>> > way, for example, I could set a screen blanking / suspend timeout but my
>> > program wouldn't have to listen to events. It would automatically be
>> > done by the framework.
>> > 
>> > Is this possible? If not, any plans to implement something like a D-BUS
>> > interface for modifying rules?
>>
>> You can already add new rules using the dbus call :
>> org.freesmartphone.Events.AddRule(s)

Is there any already-coded program that do that?  Something like
update-frameworkd-rules, for the end-user.

>> the string should be in the same format than the rules in the rules
>> file.

Is there a way to know which rules are available?  IMHO the above
update-frameworkd-rules should have a --show/--list option for that
(this reminds me of `git config` [3]...).

>> For the way to modify rules, it is planned. Rules can have name (using
>> 'name' attribute in the rules file.)
>> I will take some time today to add a RemoveRule, so that you can add and
>> remove rules.
>
> Ok I added the RemoveRule method to oeventsd, you can check oevents.py
> in the framework tests directory to see how to add and remove rules.
>
> BUT, it makes me realize a problem : the rules manager only activates
> the rules that are specified in the rules preference file (e.g [0])
>
> So if you add a new rule with a name, the rule won't be activated unless
> you also specify that the rule is activated in the preference file. that
> is not very good and we need to solve this problem.

The whole story above led me thinking about how Debian should manage
these rules.  The main problem here is that Debian must ship a working
setup, which at the same time should be configurable through Debian
packages, as I explained at [4].

What's upstream plan?  Having one unique rules file or splitting the
configuration into single and more specific ones?  Something like
sounds.yaml (ring- and message-tones plus volumes), etc.?

Thx, bye,
Gismo / Luca

>  [0] :
> http://git.freesmartphone.org/?p=framework.git;a=blob;f=etc/freesmartphone/opreferences/conf/rules/default.yaml;h=e0066eff76973b5597d879bf81b0e0f490660bdb;hb=HEAD
[1] http://www.freesmartphone.org/index.php/Infrastructure#Mailing_Lists
[2] http://wiki.debian.org/Teams/DebianFSO
[3] http://www.kernel.org/pub/software/scm/git/docs/git-config.html
[4] http://lists.linuxtogo.org/pipermail/smartphones-userland/2008-October/000327.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 314 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-fso-maint/attachments/20081030/0ab63156/attachment.pgp