Dominig,
>>>
>>> As long as Genivi is happy to work without any security, that will
>>> work.
>> That's a very silly statement, Dominig. Are you nowadays trying to make
>> cooperation difficult, or is it only by mistake?
>
> It might just be control of nuances in language, I do like to been seen
be compliant but to be the most
attractive implementation of a Genivi compliant system.
>
> Dominig
2014-10-30 17:54 GMT+01:00 Andersson, Gunnar :
> Dominig,
>
>> From: Dominig Ar Foll [mailto:dominig.arf...@fridu.net]
>> Sent: den 24 oktober 2014 04:06
>> To: And
Dominig,
> From: Dominig Ar Foll [mailto:dominig.arf...@fridu.net]
> Sent: den 24 oktober 2014 04:06
> To: Andersson, Gunnar
> Cc: genivi-...@mail.genivi.org; ivi@lists.tizen.org; Bourcier, Frédéric
> (frederic.bourc...@windriver.com)
> Subject: Re: Tizen and GENIVI yocto lay
2014-10-22 17:04 GMT+02:00 Andersson, Gunnar :
> Hello all
>
>
>
> 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.
>
> The reasons might be, (and I'm speculating here so fe
On Thu, 2014-10-23 at 11:19 +, Andersson, Gunnar wrote:
> > > 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 t
izen and GENIVI yocto layers, and future of IVI builds
>
> On Wed, 2014-10-22 at 15:04 +, 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
> > "
On Wed, 2014-10-22 at 15:04 +, 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.
>
