From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: openembedded-devel@lists.openembedded.org
Subject: Re: defining FEATURE_PACKAGES_* in core-image.bbclass vs image.bbclass
Date: Mon, 14 Jul 2014 20:39:14 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.11.1407142038250.8059@localhost> (raw)
In-Reply-To: <CA+gsK-rJHEnF_KmNFmq_1KqW7wfLBnMLpKWpFBeQYvAHFZM_cg@mail.gmail.com>
On Mon, 14 Jul 2014, Rudolf Streif wrote:
> > is there something special about hwcodecs that suggests it
> > should stay in core-image rather than moving to image as well? i'm
> > just trying to understand the rationale.
> >
> Not necessarily. But I would consider them extended features and
> they belong into core-image in my opinion. Not all embedded systems
> need them. Many don't have video or audio support. I would even
> suggest to move splash to core-image. If a device does not have
> video there is not reason for a splash screen.
>
> I consider debug-tweaks, package-management, and readonly-rootfs the
> basic image features to be in image.
and i have no problem with that rationale. :-)
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next prev parent reply other threads:[~2014-07-15 0:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-14 19:05 defining FEATURE_PACKAGES_* in core-image.bbclass vs image.bbclass Robert P. J. Day
2014-07-14 22:43 ` Rudolf Streif
2014-07-14 23:22 ` Robert P. J. Day
2014-07-15 0:36 ` Rudolf Streif
2014-07-15 0:39 ` Robert P. J. Day [this message]
2014-07-15 11:02 ` Robert P. J. Day
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=alpine.LFD.2.11.1407142038250.8059@localhost \
--to=rpjday@crashcourse.ca \
--cc=openembedded-devel@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox