Re: [yocto] BAD_RECOMMENDATIONS / BAD_RECOMMENDS not working

2013-10-26 Thread Martin Jansa
Add .bbappend for packagegroup-core-qt4e and remove qt-demo-init from RDEPENDS_${PN} there. On Fri, Oct 25, 2013 at 5:38 PM, Diego Sueiro wrote: > > 2013/10/25 Martin Jansa > >> BAD_RECOMMENDATIONS work only for packages which are installed because >> something has them in RRECOMMENDS, if your

Re: [yocto] BAD_RECOMMENDATIONS / BAD_RECOMMENDS not working

2013-10-25 Thread Diego Sueiro
2013/10/25 Martin Jansa > BAD_RECOMMENDATIONS work only for packages which are installed because > something has them in RRECOMMENDS, if your custom image has qt-demo-init in > IMAGE_INSTALL or pulled by RDEPENDS in some variable, than it won't be > removed (and shouldn't be). > Thanks Martin,

Re: [yocto] BAD_RECOMMENDATIONS / BAD_RECOMMENDS not working

2013-10-25 Thread Martin Jansa
BAD_RECOMMENDATIONS work only for packages which are installed because something has them in RRECOMMENDS, if your custom image has qt-demo-init in IMAGE_INSTALL or pulled by RDEPENDS in some variable, than it won't be removed (and shouldn't be). Use bitbake -g to see why and how it's pulled to you

[yocto] BAD_RECOMMENDATIONS / BAD_RECOMMENDS not working

2013-10-25 Thread Diego Sueiro
Folks, I'm using dylan branch and package management is ipk. I'm trying to remove qt-demo-init package from my custom image with both BAD_RECOMMENDATIONS and BAD_RECOMMENDS variables but it is still being installed on rootfs. I've already did a cleansstate on my image recipe but no success. I c