Patrick, > -----Original Message----- > From: Patrick Ohly [mailto:[email protected]] > Sent: den 23 oktober 2014 08:17 > To: Andersson, Gunnar > Cc: [email protected]; [email protected]; Bourcier, Frédéric > ([email protected]) > Subject: Re: Tizen and GENIVI yocto layers, and future of IVI builds > > On Wed, 2014-10-22 at 15:04 +0000, Andersson, Gunnar wrote: > > For yocto/oe based builds, the recipes for newly developed software > > from GENIVI plus the baseline image definitions are in the layer named > > "meta-ivi" at the yocto project, and I suppose they will stay there for a > > while at least. > > > > OTOH meta-tizen seems a bit intrusive to me. It appears to essentially > > repackage a lot of components using its own build scripts, including > > the adopted GENIVI components. > > That's just because meta-tizen at the moment is a proof-of-concept > showing that that tools (with some patches, which are going to be in > Yocto 1.7) are suitable for building Tizen.
OK, thanks for confirming. I only brought up the discussion because people were asking how things are built. > > The real goal is to turn meta-tizen into a Yocto-compliant layer that > only adds the Tizen-specific .bb and .bbappend files. For example, it > would be preferable to use a GENIVI-maintained layer for GENIVI > components. Sounds like we are in agreement. > > > One could propose to rename the layer to meta-genivi but in the long term as > > GENIVI-initiated implementation projects become adopted, the distinction of > > which project they belong to would be of less importance. I'm hoping the > > same > > would hold true for Tizen IVI. Project-specific layers should be focused > > primarily on defining distro/image content and necessary tweaks, as opposed > > to > > build scripts for upstream components, IMHO. Maybe in such a future the > > generic name (meta-ivi) will again make sense so I'm not proposing to rename > > now. > > I think the name is okay, as long as the layers inside the repo stay > clean and don't duplicate the work done elsewhere. > > > Just to complete the picture I want to mention that GENIVI components are > > also > > built in non-Yocto baselines such as with Baserock, (and Tizen IVI also > > keeps its > > OBS/GBS based build?) GENIVI has for a long time also discussed providing > > at least a development environment based on some standard distro, > > (think GENIVI-software in Debian packaging as an example), and there are > > signs of target platforms/distros created using those principles too. > > When I looked at your baseline image I came away with the impression > that it really is (meant to be!) just a very minimal collection of > essential packages, and not something that can really be used for > testing more complex functionality. Your demo platform gets closer, but > even that describes running apps as root, which IMHO still misses > essential pieces like user session management. I don't understand the relevance of this part. The principle remains the same for all IVI related builds, big or small. > > I hope that once we have cleaned up meta-tizen, it might be also useful > for folks looking for a more complete GENIVI-compliant distro. > > -- > Best Regards, Patrick Ohly > > The content of this message is my personal opinion only and although > I am an employee of Intel, the statements I make here in no way > represent Intel's position on the issue, nor am I authorized to speak > on behalf of Intel on this matter. - Gunnar -- Gunnar Andersson Lead Architect, GENIVI Alliance Infotainment, Volvo Car Corporation _______________________________________________ IVI mailing list [email protected] https://lists.tizen.org/listinfo/ivi
