Fahad, > Date: Thu, 6 Jun 2013 09:54:01 +0500 > From: Fahad Usman <[email protected]> > To: [email protected] > Subject: [yocto][meta-ivi][PATCH] packagegroups: restructure the > yocto-ivi PGs > Message-ID: <[email protected]> > > with the current implementation of packagegroups, it's not clear > how a particular recipe map to the GENIVI baseline document. > > this scheme remove confusion about which packagegroup a certain > recipe belong to. And provide guidance to the customers about > modifying the image. For instance customers should be careful about > replacing specific-p1 components if they wish to maintain GENIVI > compliance. [...]
It is correct that GENIVI compliance differentiates the components on two properties (two priorities and three types). However, I would assert that not all of the resulting 6 combinations are really relevant for the meta-ivi implementation. Personally, I would say that from the implementer perspective two things really matter: (1) the component priority and (2) the possibility to exchange component's implementation. (1) is already reflected by the existing packagegroups (-core-p1 and -core-p2). For (2), abstract and placeholder components can be treated the same way (since they both allow to freely choose the implementation). These would leave us with 4 different categories (instead of 6 as proposed). For naming purposes I would suggest something like '-p1/p2-fixed/variable' (although I must admit that these names do not yet feel 100% right). There is an additional complication to be considered. In some cases, components with different priority/variability (and therefore belonging to different packagegroups) are produced from the same source tree. For example AudioManager comes with the daemon and default plug-in. However, while the daemon is P1/specific, the plug-ins are P2/abstract. Regards, --Pavel Konopelko Visteon Innovation & Technology GmbH Sitz der Gesellschaft/Place of Business: Kerpen Registergericht: Köln HRB 71036 Geschäftsführung/Management Board: Christian Feltgen _______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yocto
