From: Khem Raj <raj.khem@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 03/16] libusb1: Address unpackaged files warning
Date: Wed, 29 Feb 2012 20:44:29 -0800 [thread overview]
Message-ID: <4F4EFEAD.9010508@gmail.com> (raw)
In-Reply-To: <008428eeaf897d9d18e070097cfc82e706913539.1330004039.git.richard.purdie@linuxfoundation.org>
On 02/23/2012 05:38 AM, Richard Purdie wrote:
> WARNING: For recipe libusb1, the following files/directories were installed but not shipped in any package:
> WARNING: /lib/libusb-1.0.la
>
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> ---
> meta/recipes-support/libusb/libusb1_1.0.8.bb | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/meta/recipes-support/libusb/libusb1_1.0.8.bb b/meta/recipes-support/libusb/libusb1_1.0.8.bb
> index e45a9d9..b8fa790 100644
> --- a/meta/recipes-support/libusb/libusb1_1.0.8.bb
> +++ b/meta/recipes-support/libusb/libusb1_1.0.8.bb
> @@ -6,7 +6,7 @@ SECTION = "libs"
> LICENSE = "LGPLv2.1+"
> LIC_FILES_CHKSUM = "file://COPYING;md5=fbc093901857fcd118f065f900982c24"
>
> -PR = "r3"
> +PR = "r4"
>
> SRC_URI = "${SOURCEFORGE_MIRROR}/libusb/libusb-${PV}.tar.bz2"
>
> @@ -27,4 +27,4 @@ do_install_append() {
>
> FILES_${PN} += "${base_libdir}/*.so.*"
>
> -FILES_${PN}-dev += "${base_libdir}/*.so"
> +FILES_${PN}-dev += "${base_libdir}/*.so ${base_libdir}/*.la"
why not just delete it. We have been living without it anyway
next prev parent reply other threads:[~2012-03-01 4:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 13:38 [PATCH 00/16] Various fixes, mostly for WARNING messages Richard Purdie
2012-02-23 13:38 ` [PATCH 01/16] eglibc: Fix package warning Richard Purdie
2012-02-23 13:38 ` [PATCH 02/16] rpm: Fix LICENSE field Richard Purdie
2012-02-23 13:38 ` [PATCH 03/16] libusb1: Address unpackaged files warning Richard Purdie
2012-03-01 4:44 ` Khem Raj [this message]
2012-02-23 13:38 ` [PATCH 04/16] libusb-compat: " Richard Purdie
2012-02-23 14:53 ` Otavio Salvador
2012-02-24 0:13 ` Richard Purdie
2012-02-23 13:38 ` [PATCH 05/16] readline: Add a patch to remove the redundant rpath linker option Richard Purdie
2012-02-23 13:38 ` [PATCH 06/16] libgcrypt: Fix unpackaged file warning Richard Purdie
2012-02-23 13:38 ` [PATCH 07/16] dbus: Fix unpackaged files warning Richard Purdie
2012-02-23 13:38 ` [PATCH 09/16] cracklib: Fix unpackaged files warning by disabling autodetected python Richard Purdie
2012-02-23 13:38 ` [PATCH 10/16] glib-2.0: Fix unpackaged files warning Richard Purdie
2012-02-23 13:38 ` [PATCH 12/16] package.bbclass: Remove empty directories created as part of srcdebug handling Richard Purdie
2012-02-23 13:38 ` [PATCH 14/16] autotools.bbclass: Make builds deterministic Richard Purdie
2012-02-23 13:38 ` [PATCH 15/16] gthumb: Resolve staticdev QA warnings Richard Purdie
2012-02-23 13:38 ` [PATCH 16/16] sstatesig.py: Add handling for machine specific module depenedencies Richard Purdie
2012-02-23 14:41 ` Martin Jansa
2012-02-23 14:48 ` [PATCH 08/16] e2fsprogs: Fix unpackaged file warning Richard Purdie
2012-02-23 14:48 ` [PATCH 11/16] dbus-glib: Correctly package bash completion pieces to avoid QA warning Richard Purdie
2012-02-23 14:48 ` [PATCH 13/16] insane.bbclass: Only depend on desktop-file-utils-native when we need it Richard Purdie
2012-02-23 14:56 ` [PATCH 00/16] Various fixes, mostly for WARNING messages Otavio Salvador
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=4F4EFEAD.9010508@gmail.com \
--to=raj.khem@gmail.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