Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: should all class files be inherited by *something*?
Date: Mon, 02 Apr 2012 22:39:20 +0100	[thread overview]
Message-ID: <1695746.vzEQQB1zRy@helios> (raw)
In-Reply-To: <alpine.DEB.2.02.1204021730530.6159@oneiric>

On Monday 02 April 2012 17:34:26 Robert P. J. Day wrote:
>   poking around the meta/classes/*.bbclass files and one looked a bit
> odd -- scons.bbclass.  i was under the impression that class files
> were supposed represent a *general* kind of functionality so i was
> curious as to what this file represented.
>
>   more to the point, it doesn't look like anything in oe-core inherits
> that class.  so what exactly is its purpose?

I believe it's for supporting the scons build system. scons isn't hugely 
popular though so I guess it's not surprising that nothing in OE-Core uses it.

>   and following up on that, another example of that kind of file is
> oelint.bbclass -- again, i don't see anything in oe-core that inherits
> it.

I think oelint.bbclass is a really out-of-date recipe lint checking tool. I 
wonder if anyone has used it lately. There could be value in bringing it up-
to-date though.

It's worth noting that we may have a number of classes that are supposed to be 
generally useful in OE-Core that aren't used within OE-Core itself. This is a 
good idea because it reduces the proliferation of different versions of such 
classes in multiple layers.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



  reply	other threads:[~2012-04-02 21:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-02 21:34 should all class files be inherited by *something*? Robert P. J. Day
2012-04-02 21:39 ` Paul Eggleton [this message]
2012-04-02 21:39 ` Chris Larson
2012-04-02 21:41   ` 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=1695746.vzEQQB1zRy@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=rpjday@crashcourse.ca \
    /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