[pkg-fso-maint] [Debian] fso-frameworkd now device-agnostic

Wed Nov 5 03:15:06 UTC 2008

Hi there!

Please read carefully this mail *before* upgrading to the latest
fso-frameworkd, i.e. version 0.2.0-git20080909-7.

The short story: the configuration and sound files have been sm'asto
their packages, thus you need to also install the fso-config-gta02
package, which will in turn pull the fso-sounds-openmoko-nonfree one.
The former contains everything is needed for the Openmoko GTA02 Neo
FreeRunner, the latter contains upstream FSO ring- and message-tones.

Speaking of commands, this means:

  $ apt-get update
  $ apt-get upgrade
  $ apt-get install fso-config-gta02

Then, you can either reboot or just restarting both fso-frameworkd and
your login manager (nodm if you use the Debian default installation).

Please report any problem you encounter *after* having read this mail in
full and the relevant thread linked below.  FYI, the Debian FSO Team [1]
can be contacted at the smartphones-userland [2] mailing list.

Now a more detailed story: because of the changes above, any upgrade
From previous versions requires manual intervention.  This is caused by
the fact that the fso-frameworkd binary package does not install anymore
the general configuration file (/etc/frameworkd.conf), which is needed
for frameworkd to start.  However, to allow the fso-frameworkd package
installation, the fso-frameworkd init script does not produce any error
if it does not find /etc/frameworkd.conf.  Instead, it tells the user to
check the /usr/share/doc/fso-frameworkd/README.Debian file (attached at
the end of this mail as well).

This decision was taken to avoid any unnecessary dependencies and also
to leave to the user the power to choose which package he wants to
install.  A more detailed discussion about the fso-config-* packages is
available at [3] (later continued at [4]), while the one about the
fso-sounds-* packages is at [5] (this ones continues at [6]).

Thx, bye,
Gismo / Luca
on behalf of the pkg-fso team:
   Joachim Breitner
   Philipp Kern
   Jan Lübbe

Footnotes: 
[1] http://wiki.debian.org/Teams/DebianFSO
[2] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
[3] http://lists.alioth.debian.org/pipermail/pkg-fso-maint/2008-October/000258.html
[4] http://lists.alioth.debian.org/pipermail/pkg-fso-maint/2008-November/000284.html
[5] http://lists.linuxtogo.org/pipermail/smartphones-userland/2008-October/000329.html
[6] http://lists.linuxtogo.org/pipermail/smartphones-userland/2008-November/000347.html

--8<---------------cut here---------------start------------->8---
fso-frameworkd for Debian
-------------------------

Debian ships a device-agnostic FSO frameworkd.  For this reason,
fso-frameworkd alone will not even start, because it is missing the
configuration files.

Strictly speaking, to start, FSO frameworkd needs only the main
configuration file, namely /etc/frameworkd.conf (of which an example
is in /usr/share/doc/fso-frameworkd/examples/frameworkd.conf).
However, to fully use FSO-frameworkd, please install the appropriate
fso-config-* and fso-sounds-* packages.

* fso-config virtual package

Whenever frameworkd is known to work on a specific device, a Debian
package should be created, containing all the necessary configuration
files: mandatory are frameworkd.conf and the scenario ones, but the
package can also ship other files as needed (e.g. a udev rules file or
the opreferences ones).  The package must provide the virtual package
fso-config and its name must be in the form fso-config-$DEVICE.  The
fso-config-general package can be used as an example.

If you want to know a list of all availables fso-config-* package,
please use `apt-cache showpkg fso-config`, section "Reverse Provides".

* fso-sounds virtual package

At least two sound files are needed, the ring- and message-tones, to
be placed in /usr/share/sounds.  Each package shipping these two
sounds must provide the virtual package fso-sounds and its name must
be in the form fso-sounds-$ORIGIN.

The default upstream FSO frameworkd profile lists these sounds in
/etc/freesmartphone/opreferences/conf/phone/default.yaml.  However, to
allow an easier customization, each fso-sounds-* package should
provide a phone file named after the $ORIGIN part of the package name,
to be installed into /usr/share/fso-sounds-rules.  This file should
then be registered as an alternative for the upstream default file
through update-alternatives.  The fso-sounds-none package can be used
as an example.

If you want to know a list of all availables fso-sounds-* package,
please use `apt-cache showpkg fso-sounds`, section "Reverse Provides".

* local configuration for the ring- and message-tones

If you do not want to install any fso-sounds-* package at all, you
should create your own local configuration file and register it as an
alternative for the upstream default file through update-alternatives.
The local configuration must have the highest alternative priority to
preserve it as the default alternative in case an fso-sounds-* package
is installed.

NB, sounds file should be in /usr/share/sounds and the extension
    should always be specified.

Please follow these commands:

  $ cat <<EOF >/usr/local/share/fso-frameworkd-default-sounds-local.yaml
    # Debian ring- and message-tones configuration: local
    ring-tone: "$RING_FILE"
    ring-volume: $RING_VOLUME
    message-tone: "$MESSAGE_FILE"
    message-volume: $MESSAGE_VOLUME
    EOF
  $ update-alternatives \
	--install \
	/etc/freesmartphone/opreferences/conf/phone/default.yaml \
	fso-frameworkd-default-sounds.yaml \
	/usr/local/share/fso-frameworkd-default-sounds-local.yaml \
	100

Check the update-alternatives manpage for further information about
how to manage the different alternatives.

 -- Luca Capello <luca at pca.it>, Mon,  3 Nov 2008 23:57:36 +0100
--8<---------------cut here---------------end--------------->8---
-------------- 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/20081105/73fce7c0/attachment-0001.pgp 