Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Paul Eggleton <paul.eggleton@linux.intel.com>,
	"Burton, Ross" <ross.burton@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/2] meta.bbclass: set INHIBIT_DEFAULT_DEPS
Date: Tue, 19 Apr 2016 08:20:06 +0100	[thread overview]
Message-ID: <1461050406.9308.226.camel@linuxfoundation.org> (raw)
In-Reply-To: <2192667.VMn04Uynna@peggleto-mobl.ger.corp.intel.com>

On Tue, 2016-04-19 at 15:33 +1200, Paul Eggleton wrote:
> On Mon, 18 Apr 2016 21:27:25 Burton, Ross wrote:
> > On 18 April 2016 at 03:57, Robert Yang <liezhi.yang@windriver.com>
> > wrote:
> > > The recipe which inherits meta.bbclass doesn't require any
> > > default deps.
> > 
> > meta is only inherited by one class (populate_sdk_base.bbclass) and
> > three
> > recipes (two of which indirectly inherit populate_sdk_base) so do
> > we really
> > need this class?  Maybe we should drop it in the 2.2 cycle.
> 
> I don't think we ought to be in too much of a hurry to remove this -
> it's 
> still a handy class. Besides I was planning on using it to solve this
> issue:
> 
>   https://bugzilla.yoctoproject.org/show_bug.cgi?id=9257 

I have the opposite view. Its pretty much impossible to tell what a
"meta" class would do from its name or have any idea of whether a given
change should be added to the class since its purpose is so vague.

I'l like to see it renamed to something more useful, or removed given
its just two lines...

Cheers,

Richard


      reply	other threads:[~2016-04-19  7:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-18  2:57 [PATCH 0/2] fix buildtools-tarball and meta.bbclass Robert Yang
2016-04-18  2:57 ` [PATCH 1/2] buildtools-tarball.bb: fix unexpected operator Robert Yang
2016-04-18  2:57 ` [PATCH 2/2] meta.bbclass: set INHIBIT_DEFAULT_DEPS Robert Yang
2016-04-18 20:27   ` Burton, Ross
2016-04-19  1:23     ` Robert Yang
2016-04-19  3:33     ` Paul Eggleton
2016-04-19  7:20       ` Richard Purdie [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=1461050406.9308.226.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.com \
    --cc=ross.burton@intel.com \
    /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