[pkg-fso-maint] breakage ahead

[Heiko Stübner]

Hi,

Am Mittwoch 13 Januar 2010 schrieb Jonas Smedegaard:
> I fail to understand how it is considered most beneficial to reinvent
> the wheel of config file handling instead of using the good old dpkg
> conffile mechanism and then handle multiple config flavors by packaging
> multiple binary packages from same source package.

I'm at the moment not sure what the best possible solution would be. So I will 
try to list the ones we discussed with pros and cons I remember:

1.) fso-config-DEVICE standalone (current one)
+ uses packaging system for conffile handling
+ includes alsa state-files
+ least work needed (as we are undermanned)
- duplicates configs for e.g. calypso (fsogsmd)


2.) fso-config-DEVICE depends on fsogsmd-config-calypso, ...
+ uses packaging system for conffile handling
+ doesn't duplicate configs
- multitude of packages with a 1kb config file in each
- what about e.g. fsodtld (date-time-location) which gets data from different 
systems


3.) daemon-pkg determines device and symlinks/copies config file
+ prevent packaging overhead
+ each daemon can select apropriate device settings
- duplicate handling of conffiles (including breakage in cornercases)
- where to put alsa states

Personally I would prefer (1.) at the moment simply because it doesn't need 
much work, will scale well for many different device types without putting us 
in dependency hell and doesn't require great new logic in the packages to 
determine for example gsm-modem variants. I.e. I would think it's not the 
common case for identical gsm-modems in different phones to always need the 
same config.


Oh, by the way the fso-usaged from yesterday includes the fixes for resume 
handling Mickey did at the end of last year.

Heiko