[pkg-fso-maint] frameworkd and how to ship rule files (was Re: FSO Control - New Project and Initial Package)
digger vermont
dv_mlist at verizon.net
Sat Nov 1 23:50:28 UTC 2008
On Sat, 2008-11-01 at 21:54 +0100, Luca Capello wrote:
> Hi there!
Hi Luca,
> I cc:ed the pkg-fso-maint mailing list to be sure everyone in the Debian
> FSO Team reads this.
>
> On Fri, 31 Oct 2008 22:56:31 +0100, digger vermont wrote:
> > On Fri, 2008-10-31 at 16:57 +0100, yves mahe wrote:
> >> 1) I think we have a conflict with zhone about pressing the POWER button.
...
>
> However, I don't think adding fso-rules-* packages is a good idea: I
> expect that everything related to the PWR button can be defined in a
> single button-pwr.yaml file, the same being true for the AUX button
> (button-aux.yaml). And a whole package for one single file is out of
> question, sorry. Moreover, do you expect an fso-rules-* package for
> each rule files? BTW, the name for such a package should be
> fso-frameworkd-rules-*...
>
I know very little about package creation, deb or ipk. What you say
makes sense.
> Since Debian by default would like to ship what the FSO image ships [3],
> the solution can be:
>
> 1) strictly follow upstream (i.e. FSO) solution
>
> 2) something similar to the fso-sounds-* packages, i.e. button-*.yaml
> are managed through update-alternatives and then fso-config-$DEVICE
> and fso-control can both provide an alternative
>
> 3) fso-config-$DEVICE does not provide any button configuration and
> anyone installing fso-control must configure frameworkd
>
Seems like the desired solution would be one that is also
distribution-agnostic.
SeeYa,
digger
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : http://lists.alioth.debian.org/pipermail/pkg-fso-maint/attachments/20081101/8c612ae1/attachment.pgp
More information about the pkg-fso-maint
mailing list