From: Joshua Lock <josh@linux.intel.com>
To: poky@yoctoproject.org
Subject: [RFC PATCH 0/1] Can we drop Clutter bbappends?
Date: Tue, 15 Nov 2011 16:16:01 -0800 [thread overview]
Message-ID: <cover.1321402302.git.josh@linux.intel.com> (raw)
All,
The subject says it all. My reading of recent changes in oe-core around X and
clutter lead me to believe that our bbappend is redundant so I'm proposing we
drop it.
Both virtual/libgl being in DEPENDS and passing the --with-flavour=glx option
are part of the standard clutter.inc now.
I may well be wrong but I like patches as a way to start discussion.
Cheers,
Joshua
Please review the following changes for suitability for inclusion. If you have
any objections or suggestions for improvement, please respond to the patches. If
you agree with the changes, please provide your Acked-by.
The following changes since commit fa81f8dfb7a342e355b608aa4204cf23ed2b251c:
mime.bbclass: fix typo (2011-11-15 12:05:30 +0000)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib josh/work
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=josh/work
Joshua Lock (1):
clutter: drop unneeded bbappends
.../clutter/clutter-1.6_1.6.18.bbappend | 4 ----
.../clutter/clutter-1.8_1.8.0.bbappend | 4 ----
.../recipes-graphics/clutter/clutter_git.bbappend | 4 ----
3 files changed, 0 insertions(+), 12 deletions(-)
delete mode 100644 meta-yocto/recipes-graphics/clutter/clutter-1.6_1.6.18.bbappend
delete mode 100644 meta-yocto/recipes-graphics/clutter/clutter-1.8_1.8.0.bbappend
delete mode 100644 meta-yocto/recipes-graphics/clutter/clutter_git.bbappend
--
1.7.7.1
next reply other threads:[~2011-11-16 0:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-16 0:16 Joshua Lock [this message]
2011-11-16 0:16 ` [RFC PATCH 1/1] clutter: drop unneeded bbappends Joshua Lock
2011-11-22 11:28 ` Richard Purdie
2011-11-22 21:44 ` Joshua Lock
2011-11-21 18:47 ` [RFC PATCH 0/1] Can we drop Clutter bbappends? Joshua Lock
2011-11-30 15:46 ` Richard Purdie
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=cover.1321402302.git.josh@linux.intel.com \
--to=josh@linux.intel.com \
--cc=poky@yoctoproject.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.