From: Scott Garman <scott.a.garman@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] ncurses: fix packaging of moved libraries
Date: Wed, 14 Mar 2012 10:09:57 -0700 [thread overview]
Message-ID: <4F60D0E5.20706@intel.com> (raw)
In-Reply-To: <6E6948ED-51D0-4E19-8D09-E82DB6438AA4@dominion.thruhere.net>
On 03/14/2012 09:53 AM, Koen Kooi wrote:
>
> Op 14 mrt. 2012, om 17:36 heeft Scott Garman het volgende geschreven:
>
>> The recent move of some of the ncurses libraries to base_libdir
>> does not work with our automatic library packaging, so this
>> explicity creates packages for libncurses, libncursesw, and
>> libtinfo.
>>
>> Signed-off-by: Scott Garman<scott.a.garman@intel.com>
>
> This is still missing a PR bump for all the packages depending on ncurses. Those need to get rebuilt to unbreak the package feeds.
Ok, I will spin a v3 of the pull request to make use of do_package_split
and include a commit for bumping the PR for all recipes which DEPEND on
ncurses.
Scott
--
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center
next prev parent reply other threads:[~2012-03-14 17:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-14 16:36 [PATCH 0/1] ncurses packaging fix [v2] Scott Garman
2012-03-14 16:36 ` [PATCH 1/1] ncurses: fix packaging of moved libraries Scott Garman
2012-03-14 16:53 ` Koen Kooi
2012-03-14 17:09 ` Scott Garman [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-03-14 0:31 [PATCH 0/1] ncurses packaging fix Scott Garman
2012-03-14 0:31 ` [PATCH 1/1] ncurses: fix packaging of moved libraries Scott Garman
2012-03-14 14:57 ` Darren Hart
2012-03-14 15:00 ` Martin Jansa
2012-03-14 15:07 ` Paul Eggleton
2012-03-14 15:18 ` Darren Hart
2012-03-14 15:20 ` Paul Eggleton
2012-03-14 15:12 ` Darren Hart
2012-03-14 15:22 ` 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=4F60D0E5.20706@intel.com \
--to=scott.a.garman@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