[pkg-fso-maint] breakage ahead
Sebastian Reichel
elektranox at gmail.com
Wed Jan 13 16:15:02 UTC 2010
On Wed, Jan 13, 2010 at 04:42:24PM +0100, Heiko Stübner wrote:
>
>
> Am Mittwoch 13 Januar 2010 schrieb Sebastian Reichel:
> > On Wed, Jan 13, 2010 at 05:48:04PM +0300, Nikita V. Youshchenko wrote:
> > > > The problem is to find a way to provide the user with a ready-to-go
> > > > config for his phone.
> > >
> > > I would vote for having config files for all devices supported by a
> > > particular daemon in the package provided by that daemon. E.g.
> > > under /usr/share/packagename/configs/
> > >
> > > Then postinst could detect current hardware and copy or symlink needed
> > > config to /etc.
> > >
> > > I think that this appreach is cleaner than alternatives, and will scale
> > > to number of devices that may become supported in forceable future.
> > >
> > > Nikita
> >
> > I like the idea, but there are two problems:
> > 1. user changes in the config file
> > 2. installation via deboostrap on another device
> 1.) user puts a real file in place of the symlink
>
> 2.) some script fso-usaged-update-config (or similiar) is run in postinst in
> the absence of a config file (so if a file/symlink) is present nothing will run
> in the postinst. But when the user wants to he can run it by hand to update it
> possibly with a param indicating the device type.
ok than there's a +1 for nikita's idea from me :)
-- 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/9331c6af/attachment-0001.pgp>
More information about the pkg-fso-maint
mailing list