On 09/20/10 13:21, Riku Voipio wrote: > When we look at the usual case, for most libraries, embedding the to > the applications is not going to be a problem. There is probably > only going to be 1-3 users of that library anyways. For the few widely > used libraries, we can have them in MeeGo core. In fact most likely > they are there already (ICU, webkit). Yes there is *some* grey space > in between "few widely used" and "lots rarely used" libraries. But > that is not the *usual* case, and in order succeed we need to focus > violently on the common use case: That the developer uses mostly > libraries from MeeGo Core and sometimes a field-specific library > (sword) that no other applications need.
This observation does make sense. One can see at the statistics collected during the LSB development: - this is usage of LSB libs: http://dev.linuxfoundation.org/navigator/browse/app_stats.php?cmd=included-lib-usage - and this is for non-LSB ones: http://dev.linuxfoundation.org/navigator/browse/app_stats.php?cmd=excluded-lib-usage Probably the set of applications analyzed for LSB is not completely suitable for MeeGo (e.g., it includes different server and enterprise applications), but I guess the tendency is clear - there are not so many libs used by hundreds of applications (with ~1300 apps in total), while a lot of libraries are used by less than 1% of analyzed programs. -- Denis Silakov, ISPRAS / Linux Foundation _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
