On Fri, Nov 18, 2011 at 00:32, McClintock Matthew-B29882 <b29...@freescale.com> wrote: > On Thu, Nov 17, 2011 at 6:29 PM, Otavio Salvador > <ota...@ossystems.com.br> wrote: >> I see your point but add more "must be online" requirements is wrong >> IMO. > > It must be online though in this case?
The code you add needs to be running on target and doesn't work at rootfs built time. This is bad and adds more complications to read-only-fs support. >> This could be done with a specific package that could mangle the >> image at first boot if really need but doing it by default on oe-core >> seems the wrong way. > > Isn't that exactly what this is doing? > > Easy enough to add this to a separate recipe or bbapends elsewhere if > there is disagreement. The need to diverge from machine default is the exception and this could be handled on the image being built, as post rootfs hook or an specific package with postinst to be run at target boot to setup it, and not by default. I see possible use cases for it, I just against it being the default behaviour. -- Otavio Salvador O.S. Systems E-mail: ota...@ossystems.com.br http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core