From: "David Nyström" <david.c.nystrom@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] image.bbclass: Allow creation of meta-packages for images
Date: Thu, 12 Dec 2013 10:11:29 +0100 [thread overview]
Message-ID: <52A97DC1.8020402@gmail.com> (raw)
In-Reply-To: <1386775110.4332.90.camel@ted>
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@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
prev parent reply other threads:[~2013-12-12 9:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 14:46 [PATCH] image.bbclass: Allow creation of meta-packages for images David Nyström
2013-12-11 15:18 ` Richard Purdie
2013-12-12 9:11 ` David Nyström [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52A97DC1.8020402@gmail.com \
--to=david.c.nystrom@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.