From mboxrd@z Thu Jan 1 00:00:00 1970 Subject: Re: Need suggestion to handle COMBINED_FEATURES variable. To: poky@lists.yoctoproject.org From: "Rahul Chauhan" X-Originating-Location: Melbourne, Victoria, AU (155.190.53.4) X-Originating-Platform: Windows Chrome 101 User-Agent: GROUPS.IO Web Poster MIME-Version: 1.0 Date: Wed, 18 May 2022 09:47:37 -0700 References: In-Reply-To: Message-ID: <13088.1652892457753604005@lists.yoctoproject.org> Content-Type: multipart/alternative; boundary="Zs1iEd7s6W2jowxd9SIJ" --Zs1iEd7s6W2jowxd9SIJ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Is there any risk, If I remove it from DISTRO_FEATURES not MACHINE_FEATURES= . Actually I am using same machine file for multi devices but each device has= separate distro. and singe image file for all the devices. So in my case i can use DISTRO_FEATURES_remove from distro file. but if modifying machine.conf file then all other device will impact. so in this case, is there any way to handle COMBINED_FEATURE. Your comment will very helpful for us. Thanks=C2=A0 Again Rahul Chauhan --Zs1iEd7s6W2jowxd9SIJ Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Is there any risk, If  I remove= it from DISTRO_FEATURES not = MACHINE_FEATURES.

= Actually I am using same machine file for multi devices but each device has= separate distro.
and singe image file for all the devices.

So in my case i can use DIST= RO_FEATURES_remove from distro file.
but if modifying machine.conf fil= e then all other device will impact.

so in this case, is there any way to handle COMBINED_FEA= TURE.

Your comment will very helpful for us.

T= hanks  Again
Rahul Chauhan --Zs1iEd7s6W2jowxd9SIJ--