[yocto] Usage of yocto on different (production vs debug) scenarios

Burton, Ross ross.burton at intel.com
Mon Apr 23 08:38:33 PDT 2018


Very curious as to what book said that, because *any* example of that
happening is a bug in the recipe itself.  I wouldn't listen to it: the YP
autobuilder has a shared sstate for three distributions * four
architectures * two libc implementations and doesn't have problems.

Ross

On 23 April 2018 at 16:23, Iván Castell <icastell at nayarsystems.com> wrote:

> Thanks a lot for all your replies. I am working on a solution trying to
> get the best option of all your answers. I will come back after deciding my
> solution to share it with the community.
>
>
> Related with that shared state cache, I found some information on a e-book
> (search the text on google to find the source):
>
> "Sharing a shared state cache is possible; however, it needs to be
> approached with care. Not all changes are detected by the shared state
> cache implementation, and when this happens, some or all of the cache needs
> to be invalidated. This can cause problems when the state cache is being
> shared. The recommendation in this case depends on the use case. Developers
> working on Yocto metadata should keep the shared state cache as default,
> separated per project. However, validation and testing engineers, kernel
> and bootloader developers, and application developers would probably
> benefit from a well-maintained shared state cache."
>
>
> After reading that I'm not sure to use it because I don't understand what
> kind of "problems" can be found, and if they can be easily detected or not.
>
>
> Does some of you have any experience using a shared sstate cache?
>
>
>
>
>
> 2018-04-23 17:10 GMT+02:00 Burton, Ross <ross.burton at intel.com>:
>
>> On 20 April 2018 at 11:47, Uwe Geuder <jrswdnan22 at snkmail.com> wrote:
>> > But can you share state between distros? Isn't the purpose of distros to
>> > use different options (variable settings) so the state would always be
>> > different?
>>
>> If the input to the recipe is different then the hashes would be
>> different so the content won't conflict.  You can definitely share
>> sstate between DISTROs.
>>
>> Ross
>> --
>> _______________________________________________
>> yocto mailing list
>> yocto at yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>
>
>
> --
>
>
>
>
> *NOTA LEGAL*
> Este correo electrónico y, en su caso, cualquier fichero anexo al mismo,
> contiene información de carácter confidencial exclusivamente dirigida a su
> destinatario y se encuentra protegido por Ley. Cualquier persona distinta
> de su destinataria tiene prohibida su reproducción, uso, divulgación, copia
> o impresión total o parcial. Si ha recibido este correo electrónico por
> error, se ruega lo notifique de inmediato al remitente borrando el mensaje
> original juntamente con sus ficheros anexos. Gracias.
>
> De conformidad con lo establecido en la LOPD, NAYAR SYSTEMS SL garantiza
> la adopción de las medidas necesarias para asegurar el tratamiento
> confidencial de los datos de carácter personal. Así mismo le informamos de
> la inclusión de sus datos en un fichero bajo la responsabilidad de NAYAR
> SYSTEMS SL, con la finalidad de poder atender los compromisos derivados de
> la relación que mantenemos con usted. Si lo desea, puede ejercer sus
> derechos de acceso, rectificación, cancelación y oposición mediante un
> escrito a la siguiente dirección: info at nayarsystems.com
>
> *LEGAL NOTE*
> This email and any attachments to it contains is confidential information
> exclusively intended for the recipients. Any divulgation, copy or
> distribution to third parties is prohibited without written permission of
> NAYAR SYSTEMS SL. If you have received this e-mail in error, please notify
> the sender immediately. In accordance with Law 15/1999 of 13 December on
> the Protection of Personal Data, the NAYAR SYSTEMS SL guarantees that it
> has adopted the necessary measures to ensure the confidential treatment of
> personal information. We also inform you that you can exercise your access,
> rectification, cancellation and opposition rights by send us a mail to:
> info at nayarsystems.com
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20180423/84ccaf13/attachment.html>


More information about the yocto mailing list