> On Apr 1, 2016, at 5:38 AM, Isak Lichtenstein <isak.lichtenst...@kistler.com> > wrote: > > Hi Joël, >> >> Hi, >> >> One idea may be to create one recipe per configuration file. >> So in each image recipe, you would add one of those recipes to >> IMAGE_INSTALL_append. > > That's exactly what I'm doing now. But as my base package "A" is in a > layer that is used by other developers, I would like to enforce somehow > that every image containing this package also provides a config package > for it.
you can use bitbake diagnostics in a image post process function to implement this logic or in a bbclass which is inherited by every image you build.
signature.asc
Description: Message signed with OpenPGP using GPGMail
-- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
