Hello Carlos, On Sat, Feb 14, 2015 at 6:42 AM, Carlos Rafael Giani <[email protected]> wrote: ... > So, it would make sense to establish some sort of dependency. But how > exactly? I thought of something like this: > > RDEPENDS_gstreamer1.0-plugins-imx-imxaudio = > "gstreamer1.0-plugins-good-audioparsers" > RDEPENDS_gstreamer1.0-plugins-imx-imxvpu = > "gstreamer1.0-plugins-bad-videoparsersbad" > > but then I also need to add gstreamer1.0-plugins-good and > gstreamer1.0-plugins-bad to the DEPENDS list, otherwise I get a warning > like: > > QA Issue: gstreamer1.0-plugins-imx-imxaudio rdepends on > gstreamer1.0-plugins-good-audioparsers, but it isn't a build dependency? > [build-deps]
> But if I add these recipes to the DEPENDS variable, then the RDEPENDS spec > is pointless, isn't it? > Another option would be to use RRECOMMENDS instead of RDEPENDS, but I am not > sure if this is such a good idea. The border line between RDEPENDS and RRECOMMENDS is very thin. The rule that I use is basically: - if something requires A to run - RDEPENDS - if something is usually used with A installed - RRECOMMENDS - if something can make use of A in some cases - RSUGGESTS As you said "It is possible to install gstreamer1.0-plugins-imx packages without these other packages." it seems to be that the right one is RRECOMMENDS so all users will have those installed by default while you keep the possibility of skipping (using BAD_RECOMMENDS) for advanced users. Just for completeness, the QA issue about missing build-dependency is something we should pay attention to but it may be a false positive as in your cause you don't depends on them for building, just runtime. So you can whitelist the warning to avoid the noise but adding the depends would be wrong. -- Otavio Salvador O.S. Systems http://www.ossystems.com.br http://code.ossystems.com.br Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750 -- _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-devel
