From: Scott Garman <scott.a.garman@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/3] ncurses: move only libncurses and libtinfo to base_libdir
Date: Tue, 13 Mar 2012 15:11:42 -0700 [thread overview]
Message-ID: <4F5FC61E.1040708@intel.com> (raw)
In-Reply-To: <4F5FB36A.8020007@opendreambox.org>
On 03/13/2012 01:51 PM, Andreas Oberritter wrote:
> On 13.03.2012 03:08, Scott Garman wrote:
>> The previous approach to moving the ncurses libraries to
>> base_libdir was too aggressive, and it broke curses support
>> in python.
>>
>> Instead, move only libncurses, libncursesw, and libtinfo to
>> base_libdir and leave the remaining libraries in libdir.
>>
>> Also delete ${libdir}/terminfo as it never gets packaged to
>> avoid a QA warning.
>>
>> This fixes [YOCTO #2070] and is a partial fix for [YOCTO #1937].
>
> Hello Scott,
>
> package splitting doesn't seem to work anymore. Libs that previously had
> their own package now end up being stored in the main ncurses package.
Thanks for reporting this, Andreas. I am working on a fix for it now. My
apologies for the trouble.
Scott
--
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center
next prev parent reply other threads:[~2012-03-13 22:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-13 2:08 [PATCH 0/3] ncurses library location fix Scott Garman
2012-03-13 2:08 ` [PATCH 1/3] path.py: add make_relative_symlink method Scott Garman
2012-03-13 2:08 ` [PATCH 2/3] ncurses: move only libncurses and libtinfo to base_libdir Scott Garman
2012-03-13 20:51 ` Andreas Oberritter
2012-03-13 22:11 ` Scott Garman [this message]
2012-03-13 2:08 ` [PATCH 3/3] gettext: do not set libncurses prefix explicitly Scott Garman
2012-03-13 13:16 ` Richard Purdie
2012-03-13 19:58 ` Scott Garman
2012-03-13 5:30 ` [PATCH 0/3] ncurses library location fix Scott Garman
2012-03-13 8:09 ` Koen Kooi
2012-03-13 8:52 ` Scott Garman
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=4F5FC61E.1040708@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