From: Scott Garman <scott.a.garman@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/3] ncurses library location fix
Date: Tue, 13 Mar 2012 01:52:53 -0700 [thread overview]
Message-ID: <4F5F0AE5.8000700@intel.com> (raw)
In-Reply-To: <12986775-86F6-43E8-B0B5-20915F618CAD@dominion.thruhere.net>
On 03/13/2012 01:09 AM, Koen Kooi wrote:
>
> Op 13 mrt. 2012, om 03:08 heeft Scott Garman het volgende geschreven:
>
>> Hello,
>>
>> This pull request improves the way ncurses libraries are installed,
>> moving only libncurses, libncursesw, and libtinfo soname libs into
>> base_libdir, and leaving everything else in libdir. This is how
>> ncurses is packaged on my Ubuntu host, and doing things this way
>> fixes bug #2070 so ncurses will work within python again.
>
> Shouldn't there a PR bump for python as well in this series?
Just pushed a commit to my branch to do this.
Scott
--
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center
prev parent reply other threads:[~2012-03-13 9:01 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
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 [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=4F5F0AE5.8000700@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 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.