Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Cc: Scott Garman <scott.a.garman@intel.com>
Subject: Re: [PATCH 0/2] ncurses packaging fix [v3]
Date: Thu, 15 Mar 2012 09:27:24 -0700	[thread overview]
Message-ID: <4F62186C.3030501@linux.intel.com> (raw)
In-Reply-To: <cover.1331756004.git.scott.a.garman@intel.com>

On 03/14/2012 01:15 PM, Scott Garman wrote:
> Hello,
>
> This fixes the ncurses library packaging.
>
> v3 of this pull request uses do_split_packages to package the libraries
> in base_libdir, and includes a commit which bumps PR for all recipes
> which DEPEND on ncurses.
>
> Scott
>
> The following changes since commit 8567549a743cb5be157e7988e1f9227d91f48850:
>
>    Revert "alsa-tools: update to 1.0.25" (2012-03-14 15:53:45 +0000)
>
> are available in the git repository at:
>    git://git.pokylinux.org/poky-contrib sgarman/ncurses-pkg-fix3-oe
>    http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=sgarman/ncurses-pkg-fix3-oe
>
> Scott Garman (2):
>    ncurses: fix packaging of moved libraries
>    PR bump for all recipes that DEPEND on ncurses
>
>   meta/recipes-core/gettext/gettext_0.18.1.1.bb      |    2 +-
>   meta/recipes-core/ncurses/ncurses.inc              |    6 ++++--
>   meta/recipes-core/readline/readline_5.2.bb         |    2 +-
>   meta/recipes-core/readline/readline_6.2.bb         |    2 +-
>   meta/recipes-core/uclibc/uclibc.inc                |    2 +-
>   meta/recipes-core/util-linux/util-linux_2.21.bb    |    2 +-
>   meta/recipes-devtools/cmake/cmake.inc              |    2 +-
>   meta/recipes-devtools/gdb/gdb-common.inc           |    2 +-
>   meta/recipes-extended/bash/bash_3.2.48.bb          |    2 +-
>   meta/recipes-extended/bash/bash_4.2.bb             |    2 +-
>   meta/recipes-extended/less/less_444.bb             |    2 +-
>   meta/recipes-extended/mc/mc_4.7.5.2.bb             |    2 +-
>   meta/recipes-extended/mc/mc_4.8.1.bb               |    2 +-
>   meta/recipes-extended/procps/procps_3.2.8.bb       |    2 +-
>   meta/recipes-extended/psmisc/psmisc_22.16.bb       |    2 +-
>   meta/recipes-extended/screen/screen_4.0.3.bb       |    2 +-
>   meta/recipes-extended/texinfo/texinfo_4.13a.bb     |    2 +-
>   meta/recipes-kernel/latencytop/latencytop_0.5.bb   |    2 +-
>   meta/recipes-kernel/powertop/powertop_1.13.bb      |    2 +-
>   .../recipes-multimedia/alsa/alsa-tools_1.0.24.1.bb |    2 +-
>   meta/recipes-support/attr/attr_2.4.46.bb           |    2 +-
>   meta/recipes-support/sqlite/sqlite3_3.7.10.bb      |    2 +-
>   meta/recipes-support/vte/vte_0.28.2.bb             |    2 +-
>   23 files changed, 26 insertions(+), 24 deletions(-)
>

Merged into OE-Core

Thanks
	Sau!



      parent reply	other threads:[~2012-03-15 16:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-14 20:15 [PATCH 0/2] ncurses packaging fix [v3] Scott Garman
2012-03-14 20:15 ` [PATCH 1/2] ncurses: fix packaging of moved libraries Scott Garman
2012-03-14 20:15 ` [PATCH 2/2] PR bump for all recipes that DEPEND on ncurses Scott Garman
2012-03-15 16:27 ` Saul Wold [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=4F62186C.3030501@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=scott.a.garman@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