[OE-core] [PATCH] image.bbclass: Allow creation of meta-packages for images
David Nyström
david.c.nystrom at gmail.com
Thu Dec 12 09:11:29 UTC 2013
On ons 11 dec 2013 16:18:30, Richard Purdie wrote:
> On Wed, 2013-12-11 at 15:46 +0100, David Nyström wrote:
>> No packages were created for core-image-minimal et.c. which
>> is a known top level interface for Yocto/OE users.
>>
>> When installing from a repo, it would be good if these interfaces
>> were common. If not, users are left with
>> packagegroup-core-*, which names are not always easy to parse.
>>
>> Signed-off-by: David Nyström <david.nystrom at enea.com>
>> ---
>> meta/classes/image.bbclass | 12 ++++--------
>> 1 file changed, 4 insertions(+), 8 deletions(-)
>
> I'm not sure we can do this since there isn't one magic package group
> which represents a given image. The problem is it needs to account for
> IMAGE_FEATURES as well and I think this could end up confusing users
> more than helping them.
>
> Cheers,
>
> Richard
Hi Richard,
Yes, the package contents may vary, but should this not be up to the
distro to be able
to configure meta-packages with a common top-level api ?
I suppose we can create our own ALLOW_EMPTY meta-package recipes, where
items are RDEPEND:ed,
which in turn mirrors the contents of selected IMAGEs.
DISTRO_FEATURES and in some degree PACKAGE_CONFIG also alters package
dependencies,
and contents. I can't really see how this is different.
Br,
David
More information about the Openembedded-core
mailing list