Hi Kalle, > > thinking about this a bit more and with the background that there is > > already an existing public database, we might should just enable a > > provision driver inside the oFono core. > > > > Meaning that we can have multiple implementations of different databases > > with just different priorities. Each nicely separated in their own > > plugin and we don't bother the oFono core with where to get the data > > from. So my idea would be that the oFono core just asks to provision a > > new context. If a plugin feels responsible, then it does so. If not then > > it stays empty. > > I like the idea. Simple to implement and we get maximum extensibility. > > Are you willing to take a plugin into ofono git which would use > mobile-broadband-provider-info database? Or should people maintain the plugins > out of tree?
in general I would accept any of such plugins into the tree. However we need to be a bit careful with the priority. And of course they need to have some sort of usage. What I expect to see in long term is that we have two or three different formats. And they just differ because of the different vertical targets. > For me the best would be to have all plugins in ofono tree and > enable/disable them with configure switches. I wanna use priorities and smart detection to use them. Nothing for the user to configure. Just installing some extra packages should active its usage. And yes, I want to make it possible to build all plugins at all time. Regards Marcel _______________________________________________ ofono mailing list ofono@ofono.org http://lists.ofono.org/listinfo/ofono
