[pkg-fso-maint] breakage ahead

[Sebastian Reichel]

On Wed, Jan 13, 2010 at 11:02:06AM +0100, Heiko Stübner wrote:
> Hi,
> 
> Am Mittwoch 13 Januar 2010 schrieb Jonas Smedegaard:
> > conf-files cannot use alternatives system. Using other methods is also
> > tricky to do right - i.e. preserve user customizations etc.
> thanks for the hint
> 
> > The IMHO best - i.e. simplest and most reliable to maintain - is to ship
> > with the software using it a plain configfile, tagged by the packaging
> > mechanisms as a conffile.
> The problem is to find a way to provide the user with a ready-to-go config for 
> his phone. The daemon-configs contain only settings to make the daemon work on 
> one specific phone. So the user can't really change the behaviour of the daemon 
> with config settings as there is really only a correct one [works or not :) ] 
> for each specific phone.
> 
> So a solution would be nice to keep the user from having to edit a config where 
> he has no real choices and can only copy settings from a README :-)
> 
> Ideas?
> 
> Heiko

I guess it would be the best to put the configuration files per
daemon package and add debconf rules to the packages to configure
the important stuff. In fso-usaged's case this would be just
lowlevel = {none, openmoko, kernel26} as far as I can see.

I'm not sure if this is against the Debian policy or if it even
works, but it may be a nice idea to setup the device type in
one of FSO's base libraries, so that it must be configured only
one time. The other daemons could then ask for the device type
configured in the base library to configure their own cfg.

-- Sebastian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-fso-maint/attachments/20100113/046668ba/attachment-0001.pgp>