Hi again,
strange things, that I don't understand happen in libfso-glib.
It seems apps that use libfso-glib are missing the function declarations from
it. For example in libfsoresource:
- free_smartphone_resource_dbus_message
- free_smartphone_resource_dbus_register_object
are missing and de
On Sun, Nov 15, 2009 at 10:06:53PM +0300, Nikita V. Youshchenko wrote:
> > > as you might have seen more and more FSO 2.0 subsystems are ready for
> > > prime time, so we have to think about how configuration works for FSO
> > > 2.0. Until now I used the same method as in FSO 1.0, which is having
>
> > as you might have seen more and more FSO 2.0 subsystems are ready for
> > prime time, so we have to think about how configuration works for FSO
> > 2.0. Until now I used the same method as in FSO 1.0, which is having
> > it lumped all together in one config file. For FSO 2.0 I'm leaning
> > tow
On Sun, Nov 15, 2009 at 09:23:39AM +0100, Michael 'Mickey' Lauer wrote:
> Hi folks,
>
> as you might have seen more and more FSO 2.0 subsystems are ready for
> prime time, so we have to think about how configuration works for FSO
> 2.0. Until now I used the same method as in FSO 1.0, which is havi
On Sun, Nov 15, 2009 at 1:53 PM, Michael 'Mickey' Lauer
wrote:
> Hi folks,
>
> as you might have seen more and more FSO 2.0 subsystems are ready for
> prime time, so we have to think about how configuration works for FSO
> 2.0. Until now I used the same method as in FSO 1.0, which is having it
> l
On Sun, 15 Nov 2009 10:05:31 +0100
m...@mnet-online.de wrote:
> On Sun, 15 Nov 2009, Michael 'Mickey' Lauer wrote:
>
> > Hi folks,
>
> > as you might have seen more and more FSO 2.0 subsystems are ready for
> > prime time, so we have to think about how configuration works for FSO
> > 2.0. Until
On Sun, 15 Nov 2009, Michael 'Mickey' Lauer wrote:
> Hi folks,
> as you might have seen more and more FSO 2.0 subsystems are ready for
> prime time, so we have to think about how configuration works for FSO
> 2.0. Until now I used the same method as in FSO 1.0, which is having it
> lumped all tog
Hi folks,
as you might have seen more and more FSO 2.0 subsystems are ready for
prime time, so we have to think about how configuration works for FSO
2.0. Until now I used the same method as in FSO 1.0, which is having it
lumped all together in one config file. For FSO 2.0 I'm leaning towards
chan
