On Tue, Jul 30, 2013 at 1:05 PM, Phil Blundell <[email protected]> wrote: > On Tue, 2013-07-30 at 10:43 -0500, Mark Hatle wrote: >> That only filters out recommendations though. A good example is some x86 >> packagegroups have a requirement of 'vte'. It turns out a class of end users >> don't want 'vte'. And they have no easy way to remove it. Telling them to >> generate a new image, with a custom IMAGE_INSTALL value that includes >> everything >> except 'vte' doesn't make sense to them. > > I'm not familiar with the particular example that you mentioned, but it > sounds as though the packagegroups in question ought to be recommending > vte rather than depending on it. I think this is probably true for > packagegroup dependencies in general in fact. > > The intended semantics of RDEPENDS are that anything named in that list > is absolutely required for correct operation and can't be removed > without breaking the functionality of the package that's doing the > depending. Things that are desirable but not absolutely necessary > should be in RRECOMMENDS (and can be suppressed with > BAD_RECOMMENDATIONS), and things which are entirely optional but might > be "nice to have" should be in RSUGGESTS.
-- Otavio Salvador O.S. Systems http://www.ossystems.com.br http://projetos.ossystems.com.br Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750 _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
