On Wed, 2017-08-30 at 09:46 -0300, Otavio Salvador wrote: > On Wed, Aug 30, 2017 at 6:39 AM, Patrick Ohly <patrick.o...@intel.co > wrote: > > Let's not dig us deeper into this hole and instead split out the > > live > > boot module into its own, arch-specific recipe. > > > > Then initramfs-framework can become allarch without having to make > > layer.conf more complicated. > > I think this can be in two steps. Splitting it out makes sense as it > avoids the build of useless packages if someone is not using the live > modules but it can be another patch.
I'm not sure in which order you want to get it done: first split out, then update (i.e. remove the layer.conf change) your patch and merge that, or apply the v4 revision of your patch and later clean up (including removal of the layer.conf change)? Personally I'm in favor of first splitting out the modules. -- 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. -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core