[oe] Generating slightly different images for different IMAGE_FSTYPES

[Tom Rini]

On Fri, 2010-02-26 at 18:14 +0100, Martin Jansa wrote:
> On Fri, Feb 26, 2010 at 10:07:41AM -0700, Tom Rini wrote:
> > On Fri, 2010-02-26 at 17:54 +0100, Marcin Juszkiewicz wrote:
> > > Dnia piątek, 26 lutego 2010 o 17:39:16 Martin Jansa napisał(a):
> > > 
> > > > We're slowly stripping packages not really needed, but it would be
> > > > nice to remove whole /boot with kernel-image.
> > > 
> > > > Is there better way to solve it or should we try harder to save space
> > > >  somewhere else?
> > > 
> > > Learn about ROOTFS_POSTPROCESS_COMMAND variable present in 
> > > classes/rootfs_*.bbclass files. You can use it to launch your function after 
> > > rootfs is populated.
> > > 
> > > So for example your shr-lite-image has drop_kernel_from_boot function in which 
> > > you check "MACHINE==om-gta01" and if it is then "rm -rf /boot/uImage". After 
> > > your function all normal ext2/ubifs/jffs2/tarball images will be created 
> > > without kernel in them.
> > 
> > Or (as there's a number of ways to do this):
> > PACKAGE_REMOVE = "kernel-image-*"
> > ROOTFS_POSTPROCESS_COMMAND_om-gta01 += "opkg-cl ${IPKG_ARGS}
> > -force-depends \
> >                                 remove ${PACKAGE_REMOVE};"
> 
> This removes it from ALL FSTYPEs... not just jffs2/ubi/ubifs

I would strongly argue (especially after my last email) that you either
always want a kernel in your rootfs, because it's actually booted from,
or you never do and it's just wasting space (and just not critically so
on other devices).

-- 
Tom Rini <tom_rini at mentor.com>
Mentor Graphics Corporation