From: Tom Rini <tom_rini@mentor.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1] v2: Update ncurses
Date: Wed, 6 Apr 2011 17:50:38 -0700 [thread overview]
Message-ID: <cover.1302137428.git.tom_rini@mentor.com> (raw)
This updates ncurses to 5.9. While less of a deal for oe-core where we
had the patch we applied on top of 5.7 mirrored and referenced that
openembedded.master did not and the patch recently went away. Fortunately
there's now a 5.8 and 5.9 release of ncurses and our 5.7 + patch was
close to 5.8 making this an easy update. While at this we move most of
the important parts of ncurses_5.x.bb into ncurses.inc which has previously
been unused. Finally, we add a comment saying that invisible-island.net
may have useful additional patches.
Pull URL: git://git.openembedded.org/openembedded-core-contrib
Branch: trini/update-ncurses
Browse: http://git.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=trini/update-ncurses
Thanks,
Tom Rini <tom_rini@mentor.com>
---
Tom Rini (1):
ncurses: Update to 5.9
.../{ncurses-5.7 => ncurses-5.9}/config.cache | 0
.../{ncurses-5.7 => ncurses-5.9}/tic-hang.patch | 0
meta/recipes-core/ncurses/ncurses.inc | 256 +++++++++++++++-----
meta/recipes-core/ncurses/ncurses_5.7.bb | 246 -------------------
meta/recipes-core/ncurses/ncurses_5.9.bb | 10 +
5 files changed, 204 insertions(+), 308 deletions(-)
rename meta/recipes-core/ncurses/{ncurses-5.7 => ncurses-5.9}/config.cache (100%)
rename meta/recipes-core/ncurses/{ncurses-5.7 => ncurses-5.9}/tic-hang.patch (100%)
delete mode 100644 meta/recipes-core/ncurses/ncurses_5.7.bb
create mode 100644 meta/recipes-core/ncurses/ncurses_5.9.bb
next reply other threads:[~2011-04-07 0:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-07 0:50 Tom Rini [this message]
2011-04-07 0:50 ` [PATCH 1/1] ncurses: Update to 5.9 Tom Rini
2011-04-08 13:19 ` Richard Purdie
2011-04-09 3:15 ` [PATCH 0/1] v2: Update ncurses Saul Wold
2011-04-09 14:34 ` Tom Rini
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.1302137428.git.tom_rini@mentor.com \
--to=tom_rini@mentor.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 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.