From: Scott Garman <scott.a.garman@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/1] ncurses packaging fix
Date: Wed, 14 Mar 2012 09:49:21 -0700 [thread overview]
Message-ID: <4F60CC11.1040700@intel.com> (raw)
In-Reply-To: <20120314075108.GC3919@jama.jama.net>
On 03/14/2012 12:51 AM, Martin Jansa wrote:
> On Tue, Mar 13, 2012 at 05:31:24PM -0700, Scott Garman wrote:
>> Hello,
>>
>> This fixes the ncurses library packaging. Thanks to Andreas Oberritter
>> for pointing it out.
>
> Why not use another do_split_packages for base_libdir?
>
> Can it be used only once per recipe? are there any libs left in libdir?
Hi Martin,
This is something worth looking into, but due to the amount of testing I
feel it would need, I'm going to have to defer it. Our next release is
coming up fast, and I've been asked to focus on recipe upgrades for the
rest of this week. I have filed bug #2106 to keep track of it.
https://bugzilla.yoctoproject.org/show_bug.cgi?id=2106
Certainly anyone who has time to do proper testing on this can grab
ownership of the bug in the meantime.
Scott
--
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center
next prev parent reply other threads:[~2012-03-14 16:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
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
2012-03-14 7:51 ` [PATCH 0/1] ncurses packaging fix Martin Jansa
2012-03-14 16:49 ` Scott Garman [this message]
2012-03-14 8:22 ` Koen Kooi
2012-03-14 16:26 ` 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=4F60CC11.1040700@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