From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: RFC: classes cleanup
Date: Wed, 13 Jul 2011 12:15:26 +0100 [thread overview]
Message-ID: <201107131215.26777.paul.eggleton@linux.intel.com> (raw)
Hi all,
I was looking through classes/ the other day and I noticed a few that probably
don't need to be in oe-core. The list I came up with:
* base_srpm.bbclass - unused, refers to missing rpm_core.bbclass
* ccdv.bbclass - unused, not sure what this is for?
* flow-lossage.bbclass - unused, looks obsolete (refers to gcc 3.4)
* mozilla.bbclass - should this be in an upper layer?
* openmoko*.bbclass - should be in an upper layer
* patcher.bbclass - obsolete?
* singlemachine.bbclass - obsolete?
* srec.bbclass - appears to be something LinuxMIPS related. Not sure it
belongs in oe-core.
* tmake.bbclass - obsolete? even oe-dev doesn't use this AFAICT...
* xfce.bbclass - should this be in an upper layer?
* xlibs.bbclass - unused, obsolete?
Comments? Any others we ought to look at removing?
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next reply other threads:[~2011-07-13 11:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-13 11:15 Paul Eggleton [this message]
2011-07-13 11:22 ` RFC: classes cleanup Phil Blundell
2011-07-14 14:55 ` Richard Purdie
2011-07-14 15:15 ` Paul Eggleton
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=201107131215.26777.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@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