On Fri, Sep 7, 2018 at 7:14 PM, Khem Raj <[email protected]> wrote: > On Fri, Sep 7, 2018 at 9:54 AM Andreas Müller <[email protected]> wrote: >> >> On Fri, Sep 7, 2018 at 4:08 PM, Khem Raj <[email protected]> wrote: >> > hi Andreas >> > >> > On Fri, Sep 7, 2018 at 3:29 AM Andreas Müller <[email protected]> >> > wrote: >> >> >> >> Have a better out-of-the-box experience >> >> >> > >> > Making a recipe rdep on a meta recipe is sort of too coarse grained >> > the vice versa is expected >> > can we encode all needed recipes in rdep ? >> That just causes redundancies - what is the problem exactly? > > Not generally hard opinionated on it. But I think > packagegroups generally cater to images no to individual recipes. > Hi Khem,
The idea was to make blueman work without further ado. Adding it made blueman usable - before it could not connect to nothing. BTW: It was me who introduced blueman. When I tested - it displayed devices and since it was not a top priority I decided to take care for details later. The reason I chose to use packagegroup-tools-bluetooth is that the packages added matched exactly the needs. It even takes care for DISTRO_FEATURE pulseaudio. Regarding redundancy: I would like to to same in meta-qt5-extra/bluedevil situation is similar there. So in case something is missing or not necessary, packagegroup-tools-bluetooth is the target of interest. How about using RRECOMMEND - it is slightly less 'agressive' and makes packagegroup-tools-bluetooth not mandatory (for packagemanager other than opkg)? Andreas -- _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-devel
