From: Khem Raj <raj.khem@gmail.com>
To: Lukas Bulwahn <lukas.bulwahn@oss.bmw-carit.de>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2 1/2] boost: ensure boost to remain an empty metapackage
Date: Mon, 11 Jan 2016 12:51:53 -0800 [thread overview]
Message-ID: <3263F3BC-4801-4145-9210-12F9ADE54B5D@gmail.com> (raw)
In-Reply-To: <1451986361-10021-1-git-send-email-lukas.bulwahn@oss.bmw-carit.de>
[-- Attachment #1: Type: text/plain, Size: 2005 bytes --]
> On Jan 5, 2016, at 1:32 AM, Lukas Bulwahn <lukas.bulwahn@oss.bmw-carit.de> wrote:
>
> To ensure that boost remains an empty metapackage after version
> updates, we explicitly require boost files to be empty. If new
> libraries exist after a version update of the boost recipe,
> bitbake will emit a warning at the do_package task. For example,
> at the version update from 1.58.0 to 1.59.0, the new timer
> library is indicated with:
>
> WARNING: QA Issue: boost: Files/directories were installed but not shipped in any package:
> /usr/lib/libboost_timer.so.1.59.0
> Please set FILES such that these items are packaged. Alternatively if they are unneeded, avoid installing them or delete them within do_install.
> boost: 1 installed and not shipped files. [installed-vs-shipped]
>
> Ross Burton suggested this improvement on the openembedded-core
> mailing list during review of the boost recipe version update [1].
>
> [1] http://lists.openembedded.org/pipermail/openembedded-core/2015-December/114314.html
>
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@oss.bmw-carit.de>
> ---
> meta/recipes-support/boost/boost.inc | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/meta/recipes-support/boost/boost.inc b/meta/recipes-support/boost/boost.inc
> index 9d7fb89..7167ac3 100644
> --- a/meta/recipes-support/boost/boost.inc
> +++ b/meta/recipes-support/boost/boost.inc
> @@ -59,6 +59,7 @@ FILES_boost-test = "${libdir}/libboost_prg_exec_monitor*.so.* \
>
> # -dev last to pick up the remaining stuff
> PACKAGES += "${PN}-dev ${PN}-staticdev"
> +FILES_${PN} = “"
alternatively use PACKAGES_remove = “${PN}"
> FILES_${PN}-dev = "${includedir} ${libdir}/libboost_*.so"
> FILES_${PN}-staticdev = "${libdir}/libboost_*.a"
>
> --
> 1.9.1
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 211 bytes --]
prev parent reply other threads:[~2016-01-11 20:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 11:45 [PATCH] boost: update to 1.59.0 Lukas Bulwahn
2015-12-17 20:35 ` Burton, Ross
2015-12-18 12:57 ` Alexander Kanavin
2015-12-18 13:11 ` Alexander Kanavin
2016-01-05 9:32 ` [PATCH v2 1/2] boost: ensure boost to remain an empty metapackage Lukas Bulwahn
2016-01-05 9:32 ` [PATCH v2 2/2] boost: update to 1.60.0 Lukas Bulwahn
2016-01-05 17:31 ` Burton, Ross
2016-01-11 21:06 ` Khem Raj
2016-01-06 17:31 ` [PATCH v3] " Lukas Bulwahn
2016-01-06 21:03 ` Burton, Ross
2016-01-11 20:51 ` Khem Raj [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=3263F3BC-4801-4145-9210-12F9ADE54B5D@gmail.com \
--to=raj.khem@gmail.com \
--cc=lukas.bulwahn@oss.bmw-carit.de \
--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