From: Darren Hart <dvhart@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
Martin Jansa <martin.jansa@gmail.com>,
Scott Garman <scott.a.garman@intel.com>
Subject: Re: [PATCH 1/1] ncurses: fix packaging of moved libraries
Date: Wed, 14 Mar 2012 08:18:34 -0700 [thread overview]
Message-ID: <4F60B6CA.3040401@linux.intel.com> (raw)
In-Reply-To: <1531514.2kqRaLqA4b@helios>
On 03/14/2012 08:07 AM, Paul Eggleton wrote:
> On Wednesday 14 March 2012 16:00:33 Martin Jansa wrote:
>> isn't just
>> ALLOW_EMPTY_${PN}-libncursesw = "1"
>> enough?
>
> I suspect we don't care if the libncursesw package isn't created when wide
> character support is disabled, if so, we don't even need that.
OK, so if a package is defined and none of the files exist, bitbake will
simply not create the package - and no errors or warnings will be raised?
If so, then kindly disregard my comments.
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2012-03-14 15:28 UTC|newest]
Thread overview: 16+ 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 [this message]
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
2012-03-14 8:22 ` Koen Kooi
2012-03-14 16:26 ` Scott Garman
-- strict thread matches above, loose matches on Subject: below --
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
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=4F60B6CA.3040401@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
--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