[pkg-fso-maint] fso: state of packaging?

[Nikita V. Youshchenko]

> Am Sonntag 13 September 2009 schrieb arne anka:
> > > could you post the fsousage-portions of fso-frameworkd. Interesting
> > > would be
> > > what lowlevel-plugin you selected.
> >
> > none.
> >
> > > For example my frameworkd.conf looks like this:
> > > [fsousage]
> > > lowlevel_type = openmoko
> > >
> > > [fsousage.controller]
> > > [fsousage.lowlevel_openmoko]
> >
> > that's certainly new to me.
> > and i tried the included frameworkd.conf abd different combinations.
> > never thought of that.
> > where does one find that kind of information and shouldn't it at least
> > be included in doc?
>
> At the time I send it as patch against openmoko-files-config to this
> list for review (new commented out section in frameworkd.conf with the
> necessary options).
>
> And yesterday I pushed my changes to git.debian.org. What would be an
> ideal config situation? commented out fsousage section and recommends on
> fso-usaged or the hard way with enabled fsosuage sections and a
> dependency on fso-usaged.

Is there any rarionale not to use fso-usaged (and use implementation from 
old framework instead)?
I guess no.
Then I suggest to upload a newer version of frameworkd, that will depend in 
fso-usaged, and provide the config lines for fso-usaged.

Once there will be other devices supported by fso-usaged, it may be a 
question of postinst to tune configuration. But currenlt we may just 
hardcode.

Nikita