[pkg-fso-maint] opreferences rules

Luca Capello luca at pca.it
Sat Nov 1 20:30:53 UTC 2008


Hi Benedikt!

On Thu, 30 Oct 2008 13:45:55 +0100, Benedikt Bär wrote:
> On Thu, 2008-10-30 at 01:06 +0100, Luca Capello wrote:
>> 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.
>
> Yes, but the first part of my message was more about the framework than
> Debian.

My understanding was that everything related to frameworkd belongs to
the smartphones-userland mailing list, nevermind.

> We're not looking for a Debian specific way of adding rules, but a
> general one, which Debian could use.

This is at least a valid reason to post to the smartphones-userland
mailing list ;-)

>> 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].
>
> The above program you've mentioned would come in handy there. :)

I still think that having separate and specific rule files would be
better, e.g. something like sounds.yaml for everything related to the
ring- and message-tones.

Debian has a big problem in this regard: every modification to conffiles
(i.e. everything in /etc) must be preserved during upgrades [1].  For
this reason, the current situation is the following, explained at [2].

- fso-frameworkd: the main program, device-agnostic and with no
  configuration at all (not even for the tones)

- fso-config-$DEVICE: everyting which is needed for $DEVICE.  E.g, for
  the FreeRunner this package is called fso-config-gta02 and contains:

    /etc/pointercal
    /etc/udev/rules.d/55-gta02-neo-freerunner.rules
    /etc/freesmartphone/opreferences/conf/phone/silent.yaml
    /etc/freesmartphone/opreferences/conf/profiles/default.yaml
    /etc/freesmartphone/oevents/rules.yaml
    /etc/frameworkd.conf
    /usr/share/openmoko/scenarios/*

- fso-sounds-$ORIGIN: the ring- and message-tones, together with the
  rule files stored in /usr/share/fso-sounds and symlinked to
  /etc/freesmartphone/opreferences/conf/phone/default.yaml thanks to the
  Debian update-alternatives tool [3]

The update-frameworkd-rules program will surely be an improvement, but
while adapting the Debian situation to it is feasible, it'll require
some magic at installation/removal.

Obviously, I don't really know the correct solution :-(

Thx, bye,
Gismo / Luca

Footnotes: 
[1] http://www.debian.org/doc/debian-policy/ch-files.html#s10.7.3
[2] http://lists.linuxtogo.org/pipermail/smartphones-userland/2008-October/000327.html
[3] http://www.debian.org/doc/debian-policy/ap-pkg-alternatives.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/20081101/713e919c/attachment.pgp 


More information about the pkg-fso-maint mailing list