From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 43BD2E02BFF; Tue, 12 Jun 2018 11:02:49 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=0.8 required=5.0 tests=BAYES_00,DATE_IN_PAST_96_XX, HTML_MESSAGE, MIME_QP_LONG_LINE, RCVD_IN_DNSWL_LOW autolearn=no version=3.3.1 X-Spam-HAM-Report: * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [81.236.60.154 listed in list.dnswl.org] * 3.4 DATE_IN_PAST_96_XX Date: is 96 hours or more before Received: date * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 0.0 HTML_MESSAGE BODY: HTML included in message * 0.0 MIME_QP_LONG_LINE RAW: Quoted-printable line longer than 76 chars Received: from v-smtpout1.han.skanova.net (v-smtpout1.han.skanova.net [81.236.60.154]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 18EDEE02B63 for ; Tue, 12 Jun 2018 11:02:46 -0700 (PDT) Received: from [10.175.196.108] ([37.123.169.62]) by cmsmtp with ESMTPA id SncnfOZvn19K9Snd0fwXbN; Tue, 12 Jun 2018 20:02:46 +0200 From: Ulf Samuelsson Mime-Version: 1.0 (1.0) Date: Fri, 1 Jun 2018 12:57:26 +0200 Message-Id: <145D4539-F47A-4F76-9291-64A755794D56@emagii.com> References: In-Reply-To: To: Alan Martinovic X-Mailer: iPad Mail (15B202) X-CMAE-Envelope: MS4wfFJDno8hzsms64dt464LtZHGv1vOWxvxmewunHyM0JdzEplv0J5fFU8uL/TTd2a5qxzmAurxzCt1Yz9V9kl5DBMwYhWxZ2TwKgCnwZOi+fYK6lKw68xi T1iYlIFovYREgOeyerwa9yGEkX+5CbJeMB6chE4u39OvxgMDmliVkKNyBUnVmpOcLnlj7I9QwAA2wny21/1jn8jYkSjFpen1ACSrH6HXmYVklSdG3hK0N6wu mQGSR5JCwoA1wHXQ0XXn1QcSzqQYUEgkoDRNlJo13f4= Cc: Yocto discussion list , Damien LEFEVRE Subject: Re: Image specific configuration files X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Jun 2018 18:02:49 -0000 Content-Type: multipart/alternative; boundary=Apple-Mail-CF150E91-44A2-4E2E-9155-B9B33DA55C67 Content-Transfer-Encoding: 7bit --Apple-Mail-CF150E91-44A2-4E2E-9155-B9B33DA55C67 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable In my current project they have defined bbclass files to allow variants of r= ecipes. The recipe would then contain do_install_append_XYZ=E2=80=99s for each clas= s. BBCLASSEXTEND =3D =E2=80=9Dproduction rnd retail=E2=80=9D would ensure you would get nginx-production, nginx-rnd, nginx-retail ipks. This way you have one recipe generating three variants in the same build. Don=E2=80=99t have the source in front of me so I can=E2=80=99t share the b= bclass (right now at least) Best Regards, Ulf Samuelsson +46 722 427 437 > 1 juni 2018 kl. 12:40 skrev Alan Martinovic : >=20 > Yes, much better phrasing: >=20 > > A single bitbake invocation always builds a single distro for a specific= target machine >=20 > Thanks=20 >=20 >> On Fri, Jun 1, 2018 at 12:18 PM, Alexander Kanavin wrote: >> If a build is 'a single bitbake invocation', then yes - it builds for a s= ingle distro and for a specific target machine, but it can build multiple re= cipes (which includes multiple images, as images are defined with recipes). >>=20 >> Alex >>=20 >>=20 >> 2018-06-01 13:07 GMT+03:00 Alan Martinovic : >>> Hey Alexander, >>> you seem to have a good understanding on the concepts. >>> Would you say that: >>>=20 >>> > A build always builds a single distro >>>=20 >>> is somewhat of a rule? >>>=20 >>>=20 >>>=20 >>>=20 >>>> On Fri, Jun 1, 2018 at 11:24 AM, Alexander Kanavin wrote: >>>> I have to say defining multiple distros and then tweaking recipes accor= ding to those definitions is not a good practice, as recipes should generall= y only access DISTRO_FEATURES and otherwise be distro-agnostic. The above ip= tables scenario should be handled with different image recipes, which pull i= n (via packages) or create different configurations. >>>>=20 >>>> Alex >>>>=20 >>>> 2018-06-01 12:04 GMT+03:00 Iv=C3=A1n Castell : >>>>> I can provide more details. My custom layer has these files related wi= th distro: >>>>>=20 >>>>> my_layer/conf/distro/include/common.conf >>>>> my_layer/conf/distro/develop.conf >>>>> my_layer/conf/distro/production.conf >>>>> my_layer/conf/distro/integration.conf >>>>>=20 >>>>> As an example of the previous files, my_layer/conf/distro/include/deve= lop.conf has this content: >>>>>=20 >>>>> require conf/distro/include/common.conf >>>>> DISTRO =3D "my-distro-development" >>>>> DISTRO_NAME =3D "OS Development" >>>>> DISTRO_STAGE =3D "development" >>>>> # And here more customizations as setting root password, PRSERV_HO= ST, or PACKAGE_FEED_URIS >>>>>=20 >>>>> In common.conf I define all features common to all my distros (PACKAGE= _CLASSES and so on) >>>>>=20 >>>>> I have custom iptables rules, then I have different files for that rul= es: >>>>>=20 >>>>> my/layer/recipes-extended/iptables/files/iptables.rules.developmen= t >>>>> my/layer/recipes-extended/iptables/files/iptables.rules.production= >>>>> my/layer/recipes-extended/iptables/files/iptables.rules.integratio= n >>>>>=20 >>>>> I use a bbappend recipe for iptables, modifiying do_install_append tas= k like this: >>>>>=20 >>>>> install -m 0600 ${WORKDIR}/iptables.rules.${DISTRO_STAGE} ${D}/etc= /iptables/iptables.rules >>>>>=20 >>>>> I use a single image recipe to define all packages installed in my fin= al image (all of them have the same set if packages, but with different cust= omizations) >>>>>=20 >>>>> Finally, I wrote a setup-build-env.sh script in my custom layer to con= figure the build easily. That script creates build-${DISTRO_STAGE}/conf/bbla= yers.conf and build-${DISTRO_STAGE}/conf/local.conf files with the proper se= tup, setting MACHINE, DISTRO and DL_DIR (shared by all distros) properly. >>>>>=20 >>>>> Hope this helps! >>>>>=20 >>>>>=20 >>>>>=20 >>>>>=20 >>>>>=20 >>>>> 2018-06-01 10:21 GMT+02:00 Alan Martinovic = : >>>>>> Hey, >>>>>> would really like to see your example. >>>>>> Am struggling to get creation of these types of images for a while no= w. >>>>>>=20 >>>>>> So far have avoided diving into multiple distros because would like t= o have the option >>>>>> of building all the images at the same time (so they are basically th= e same distro). >>>>>>=20 >>>>>>> On Fri, Jun 1, 2018 at 8:13 AM, Iv=C3=A1n Castell wrote: >>>>>>> I fixed this issue defining different distro.conf files in my custom= layer, adding a custom variable DISTRO_STAGE with the name of my distro (pr= oduction, rnd, retail, and so on), Then you setup DISTRO in your local.conf t= o the proper value you want to use. Finally you can use that DISTRO_STAGE va= riable in your custom .bb or .bbappend recipes to decide the proper configur= ation files you want to install in your final image. That works as expected.= Hope this helps! >>>>>>>=20 >>>>>>>=20 >>>>>>>=20 >>>>>>>=20 >>>>>>> 2018-06-01 7:46 GMT+02:00 Damien LEFEVRE : >>>>>>>> Hi, >>>>>>>>=20 >>>>>>>> For the same MACHINE I create the following images: >>>>>>>> - myimage-production >>>>>>>> - myimage-rnd >>>>>>>> - myimage-retail >>>>>>>>=20 >>>>>>>> The production one has production assisted tools for flashing perip= heral HW, testing vital HW components, writing some serial numbers, etc. >>>>>>>>=20 >>>>>>>> The rnd one has more packages than the retail one just to help rnd w= ork and debugging in device, but none of the rnd image extra packages.=20 >>>>>>>>=20 >>>>>>>> The retail one has the final product image. >>>>>>>>=20 >>>>>>>> I'm using web and FTP servers. I would like for the rnd version of t= he image to have a different nginx configuration to set the root directory t= o a development folder, or set an alias. >>>>>>>>=20 >>>>>>>> Furthermore, I'll have different variant of the device where only t= he device SW changes but the platform is identical. So I'll end up with=20 >>>>>>>> - myimage2-production >>>>>>>> - myimage2-rnd >>>>>>>> - myimage2-retail >>>>>>>>=20 >>>>>>>> I know how to make MACHINE based configuration. How could I do this= in my nginx.bbappend based on image name? >>>>>>>>=20 >>>>>>>> Thanks, >>>>>>>> -Damien >>>>>>>>=20 >>>>>>>> --=20 >>>>>>>> _______________________________________________ >>>>>>>> yocto mailing list >>>>>>>> yocto@yoctoproject.org >>>>>>>> https://lists.yoctoproject.org/listinfo/yocto >>>>>>>>=20 >>>>>>>=20 >>>>>>>=20 >>>>>>>=20 >>>>>>> --=20 >>>>>>>=20 >>>>>>>=20 >>>>>>>=20 >>>>>>>=20 >>>>>>> NOTA LEGAL >>>>>>> Este correo electr=C3=B3nico y, en su caso, cualquier fichero anexo a= l mismo, contiene informaci=C3=B3n de car=C3=A1cter confidencial exclusivame= nte dirigida a su destinatario y se encuentra protegido por Ley. Cualquier p= ersona distinta de su destinataria tiene prohibida su reproducci=C3=B3n, uso= , divulgaci=C3=B3n, copia o impresi=C3=B3n total o parcial. Si ha recibido e= ste correo electr=C3=B3nico por error, se ruega lo notifique de inmediato al= remitente borrando el mensaje original juntamente con sus ficheros anexos. G= racias. >>>>>>>=20 >>>>>>> De conformidad con lo establecido en la LOPD, NAYAR SYSTEMS SL garan= tiza la adopci=C3=B3n de las medidas necesarias para asegurar el tratamiento= confidencial de los datos de car=C3=A1cter personal. As=C3=AD mismo le info= rmamos de la inclusi=C3=B3n de sus datos en un fichero bajo la responsabilid= ad de NAYAR SYSTEMS SL, con la finalidad de poder atender los compromisos de= rivados de la relaci=C3=B3n que mantenemos con usted. Si lo desea, puede eje= rcer sus derechos de acceso, rectificaci=C3=B3n, cancelaci=C3=B3n y oposici=C3= =B3n mediante un escrito a la siguiente direcci=C3=B3n: info@nayarsystems.co= m >>>>>>>=20 >>>>>>> LEGAL NOTE >>>>>>> This email and any attachments to it contains is confidential inform= ation exclusively intended for the recipients. Any divulgation, copy or dist= ribution to third parties is prohibited without written permission of NAYAR S= YSTEMS SL. If you have received this e-mail in error, please notify the send= er immediately. In accordance with Law 15/1999 of 13 December on the Protect= ion of Personal Data, the NAYAR SYSTEMS SL guarantees that it has adopted th= e necessary measures to ensure the confidential treatment of personal inform= ation. We also inform you that you can exercise your access, rectification, c= ancellation and opposition rights by send us a mail to: info@nayarsystems.co= m >>>>>>>=20 >>>>>>>=20 >>>>>>> --=20 >>>>>>> _______________________________________________ >>>>>>> yocto mailing list >>>>>>> yocto@yoctoproject.org >>>>>>> https://lists.yoctoproject.org/listinfo/yocto >>>>>>>=20 >>>>>>=20 >>>>>=20 >>>>>=20 >>>>>=20 >>>>> --=20 >>>>>=20 >>>>>=20 >>>>>=20 >>>>>=20 >>>>> NOTA LEGAL >>>>> Este correo electr=C3=B3nico y, en su caso, cualquier fichero anexo al= mismo, contiene informaci=C3=B3n de car=C3=A1cter confidencial exclusivamen= te dirigida a su destinatario y se encuentra protegido por Ley. Cualquier pe= rsona distinta de su destinataria tiene prohibida su reproducci=C3=B3n, uso,= divulgaci=C3=B3n, copia o impresi=C3=B3n total o parcial. Si ha recibido es= te correo electr=C3=B3nico por error, se ruega lo notifique de inmediato al r= emitente borrando el mensaje original juntamente con sus ficheros anexos. Gr= acias. >>>>>=20 >>>>> De conformidad con lo establecido en la LOPD, NAYAR SYSTEMS SL garanti= za la adopci=C3=B3n de las medidas necesarias para asegurar el tratamiento c= onfidencial de los datos de car=C3=A1cter personal. As=C3=AD mismo le inform= amos de la inclusi=C3=B3n de sus datos en un fichero bajo la responsabilidad= de NAYAR SYSTEMS SL, con la finalidad de poder atender los compromisos deri= vados de la relaci=C3=B3n que mantenemos con usted. Si lo desea, puede ejerc= er sus derechos de acceso, rectificaci=C3=B3n, cancelaci=C3=B3n y oposici=C3= =B3n mediante un escrito a la siguiente direcci=C3=B3n: info@nayarsystems.co= m >>>>>=20 >>>>> LEGAL NOTE >>>>> This email and any attachments to it contains is confidential informat= ion exclusively intended for the recipients. Any divulgation, copy or distri= bution to third parties is prohibited without written permission of NAYAR SY= STEMS SL. If you have received this e-mail in error, please notify the sende= r immediately. In accordance with Law 15/1999 of 13 December on the Protecti= on of Personal Data, the NAYAR SYSTEMS SL guarantees that it has adopted the= necessary measures to ensure the confidential treatment of personal informa= tion. We also inform you that you can exercise your access, rectification, c= ancellation and opposition rights by send us a mail to: info@nayarsystems.co= m >>>>>=20 >>>>>=20 >>>>> --=20 >>>>> _______________________________________________ >>>>> yocto mailing list >>>>> yocto@yoctoproject.org >>>>> https://lists.yoctoproject.org/listinfo/yocto >>>>>=20 >>>>=20 >>>=20 >>=20 >=20 > --=20 > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto --Apple-Mail-CF150E91-44A2-4E2E-9155-B9B33DA55C67 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable In my current project they have defined bbc= lass files to allow variants of recipes.
The recipe would then contain &= nbsp;do_install_append_XYZ=E2=80=99s for each class.

BBCLASSEXTEND =3D =E2=80=9Dproduction rnd retail=E2=80=9D
<= br>would ensure you would get nginx-production, nginx-rnd, nginx-retail ipks= .

This way you have one recipe generating three var= iants in the same build.

Don=E2=80=99t have the sou= rce in front of me  so I can=E2=80=99t share the bbclass (right now at l= east)

Best Regards,
Ulf Sam= uelsson
+46 722 427 437

1 juni 2018 kl. 12:40 s= krev Alan Martinovic <alan.m= artinovic@senic.com>:

Yes, much better phrasing:

> A single bitbake invocation alwa= ys builds a single distro for a specific target m= achine

<= span style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.= 8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal= ;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text= -transform:none;white-space:nowrap;word-spacing:0px;background-color:rgb(255= ,255,255);text-decoration-style:initial;text-decoration-color:initial;float:= none;display:inline">Thanks 

On Fri, Jun 1, 2018 at 12:18 PM, Alexander= Kanavin <alex.kanavin@gmail.com> wrote:
If a build is 'a single bitbake invoc= ation', then yes - it builds for a single distro and for a specific target m= achine, but it can build multiple recipes (which includes multiple images, a= s images are defined with recipes).

Alex
<= br>
=
2018-06-01 13:07 GMT+03:00 Alan Martinovic <alan.martinovic@senic.com>:
Hey Alexander,
you seem to h= ave a good understanding on the concepts.
Would you say that:

=
> A build a= lways builds a single distro

is somewhat of a rule?




On Fri, Jun 1, 2018 at 11:24 AM= , Alexander Kanavin <alex.kanavin@gmail.com> wrote:
I have to say defining mul= tiple distros and then tweaking recipes according to those definitions is no= t a good practice, as recipes should generally only access DISTRO_FEATURES a= nd otherwise be distro-agnostic. The above iptables scenario should be handl= ed with different image recipes, which pull in (via packages) or create diff= erent configurations.

Alex

2018-06-01 12:04 GMT+03:00 Iv=C3=A1n Castell <icastell@nayarsystems.com>:
=
I can provide more details. My custom layer has these files= related with distro:

    my_layer/conf/distro/= include/common.conf
    my_lay= er/conf/distro/develop.conf
<= span style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font-size:sma= ll;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;= font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-= transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,= 255,255);text-decoration-style:initial;text-decoration-color:initial;float:n= one;display:inline">    my_layer/conf/distro/production.conf<= /span>
    my_layer/conf/distro/integration.conf

As an example o= f the previous files, my_layer/conf/distro/include/develop.conf has thi= s content:

    require con= f/distro/include/common.conf
    DISTRO =3D "my-dis= tro-development"
    DISTRO_NAME =3D "OS Development"
    DISTRO_STAGE =3D "development"
   = # And here more customizations as setting root password, PRSERV_HOST, or PA= CKAGE_FEED_URIS

In common.conf I define all fea= tures common to all my distros (PACKAGE_CLASSES and so on)

I have custom iptables rules, then I have different files for that r= ules:

    my/layer/recipes-extended/ipta<= wbr>bles/files/iptables.rules.development
    my/layer/recipes-extended/iptables/files/ipt= ables.rules.production
   = my/layer/recipes-extended/iptables/files/iptables.rules.integration

I use a bbappend recipe for iptables,= modifiying do_install_append task like this:

<= /div>
    install -m 0600 ${WORKDIR}/iptables.rules.${DIS= TRO_STAGE} ${D}/etc/iptables/iptables.rules

I use a single image recipe to define all packages installed in my final i= mage (all of them have the same set if packages, but with different customiz= ations)

Finally, I wrote a setup-build-env.sh scrip= t in my custom layer to configure the build easily. That script creates build-${DISTRO_STAGE}/conf/bblayers.conf and build-${DISTRO_STAGE}/conf/local.conf files w= ith the proper setup, setting MACHINE, DISTRO and DL_DIR (shared by all= distros) properly.

Hope this helps!

=



<= /span>
<= br>
2018-06-01 10:21 GMT+02:00 Alan Martinovic <alan.martinovic@senic.com>:
Hey,
would really like to see your example.
<= div>Am struggling to get creation of these types of images for a while now.<= /div>

So far have avoided diving into multiple distros be= cause would like to have the option
of building all the images at t= he same time (so they are basically the same distro).

=
On Fri, Jun 1, 2018 at 8:13 AM, Iv=C3=A1n Castell= <icastell@nayarsystems.com> wrote:
I fixed this issue defin= ing different distro.conf files in my custom layer, adding a custom variable= DISTRO_STAGE with the name of my distro (production, rnd, retail, and so on= ), Then you setup DISTRO in your local.conf to the proper value you want to u= se. Finally you can use that DISTRO_STAGE variable in your custom .bb or .bb= append recipes to decide the proper configuration files you want to install i= n your final image. That works as expected. Hope this helps!




2018-06-01 7:46 GMT+02:00 Damien LEFEVRE <lef= evre.da@gmail.com>:
Hi,=

For the same MACHINE I create the following images:
- myimage-production
- myimage-rnd
- myimage-retai= l

The production one has production assisted tools f= or flashing peripheral HW, testing vital HW components, writing some serial n= umbers, etc.

The rnd one has more packages than the= retail one just to help rnd work and debugging in device, but none of the r= nd image extra packages. 

The retail one has t= he final product image.

I'm using web and FTP serve= rs. I would like for the rnd version of the image to have a different nginx c= onfiguration to set the root directory to a development folder, or set an alias.

Furthermore, I= 'll have different variant of the device where only the device SW changes bu= t the platform is identical. So I'll end up with 
- myimage2-production
- myimage2-rnd
- my= image2-retail

I know how to make MACHINE based conf= iguration. How could I do this in my nginx.bbappend based on image name= ?

Thanks,
-Damien
=

--
_______________________________________________
yocto mailing list
yocto@yoctoproje= ct.org
https://lists.yoctoproject.org/listinfo/yocto



-= -




= NOTA LEGAL
Este correo electr=C3=B3nico y, en su caso, cual= quier fichero anexo al mismo, contiene informaci=C3=B3n de car=C3=A1cter con= fidencial exclusivamente dirigida a su destinatario y se encuentra protegido= por Ley. Cualquier persona distinta de su destinataria tiene prohibida su r= eproducci=C3=B3n, uso, divulgaci=C3=B3n, copia o impresi=C3=B3n total o parc= ial. Si ha recibido este correo electr=C3=B3nico por error, se ruega lo noti= fique de inmediato al remitente borrando el mensaje original juntamente con s= us ficheros anexos. Gracias.

De conformidad con lo establecido en la L= OPD, NAYAR SYSTEMS SL garantiza la adopci=C3=B3n de las medidas necesarias p= ara asegurar el tratamiento confidencial de los datos de car=C3=A1cter perso= nal. As=C3=AD mismo le informamos de la inclusi=C3=B3n de sus datos en un fi= chero bajo la responsabilidad de NAYAR SYSTEMS SL, con la finalidad de poder= atender los compromisos derivados de la relaci=C3=B3n que mantenemos con us= ted. Si lo desea, puede ejercer sus derechos de acceso, rectificaci=C3=B3n, c= ancelaci=C3=B3n y oposici=C3=B3n mediante un escrito a la siguiente direcci=C3= =B3n: info@nayarsystems.com

LEGAL NOTE
=
This email and any attachments to it contains is co= nfidential information exclusively intended for the recipients. Any divulgat= ion, copy or distribution to third parties is prohibited without written per= mission of NAYAR SYSTEMS SL. If you have received this e-mail in error, plea= se notify the sender immediately. In accordance with Law 15/1999 of 13 Decem= ber on the Protection of Personal Data, the NAYAR SYSTEMS SL guarantees that= it has adopted the necessary measures to ensure the confidential treatment o= f personal information. We also inform you that you can exercise your access= , rectification, cancellation and opposition rights by send us a mail to:&nb= sp;info@nayarsyst= ems.com


--
_______________________________________________
yocto mailing list
yocto@yoctoproje= ct.org
https://lists.yoctoproject.org/listinfo/yocto




--
<= div class=3D"m_-8649852102808283125m_7472730988948613251m_536147415239330704= 9m_7096927316469470777gmail_signature" data-smartmail=3D"gmail_signature">


NOTA LEGAL
Este correo electr=C3=B3= nico y, en su caso, cualquier fichero anexo al mismo, contiene informaci=C3=B3= n de car=C3=A1cter confidencial exclusivamente dirigida a su destinatario y s= e encuentra protegido por Ley. Cualquier persona distinta de su destinataria= tiene prohibida su reproducci=C3=B3n, uso, divulgaci=C3=B3n, copia o impres= i=C3=B3n total o parcial. Si ha recibido este correo electr=C3=B3nico por er= ror, se ruega lo notifique de inmediato al remitente borrando el mensaje ori= ginal juntamente con sus ficheros anexos. Gracias.

De conformidad con= lo establecido en la LOPD, NAYAR SYSTEMS SL garantiza la adopci=C3=B3n de l= as medidas necesarias para asegurar el tratamiento confidencial de los datos= de car=C3=A1cter personal. As=C3=AD mismo le informamos de la inclusi=C3=B3= n de sus datos en un fichero bajo la responsabilidad de NAYAR SYSTEMS SL, co= n la finalidad de poder atender los compromisos derivados de la relaci=C3=B3= n que mantenemos con usted. Si lo desea, puede ejercer sus derechos de acces= o, rectificaci=C3=B3n, cancelaci=C3=B3n y oposici=C3=B3n mediante un escrito= a la siguiente direcci=C3=B3n: info@nayarsystems.com<= /a>



--
_______________________________________________
yocto mailing list
yocto@yoctoproje= ct.org
https://lists.yoctoproject.org/listinfo/yocto




--
= _______________________________________________
yocto mailin= g list
yocto@yocto= project.org
https://lists.yoctoproject.org/listinfo/yocto
= --Apple-Mail-CF150E91-44A2-4E2E-9155-B9B33DA55C67--