Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 00/14] Warning Fixes and some Updates
Date: Wed, 14 Mar 2012 13:26:55 +0000	[thread overview]
Message-ID: <1331731615.18586.26.camel@ted> (raw)
In-Reply-To: <cover.1331713807.git.sgw@linux.intel.com>

On Wed, 2012-03-14 at 01:33 -0700, Saul Wold wrote:
> Richard,
> 
> This has some warning fixes along with some update.
> 
> Biggest change is to bitbake.conf, which re-orders PACKAGE and addes 
> ${libdir}/${BPN}/*.a to the staticdev list, this was seen in a number 
> of packages and seems to make sense.  But I would understand if there
> are other issues I am not aware of.
> 
> The FILES_${PN} was grabbing from ${libdir}/${BPN}/* so we needed to 
> get the staticdev in before that.

I replied to this patch. If we do take it in, it needs some very
specific testing data.

> Saul Wold (14):
>   owl-video: Fix unpackaged file warning
>   ltp: Package static library in -staticdev
>   quilt: Fix docs packaging warnings
>   autoconf: remove emacs mode files to fix warnings
>   rpm: Package python-rpm static archive correctly
>   distro_tracking: Updates for manual checks
>   avahi: Update to 0.6.31
>   man-pages: Update to 3.36
>   libgalago: Fix package warnings by not packaging autopackage
>   man: fix configure issue to solve warnings

I took these, thank.

>  gpgme: fix packaging warnings

I'd like to see a small tweak to this one (I've replied to the patch)

>  python: package static libraries correctly in -staticdev

I meant not to take this after the comment from Martin but accidentally
did. I therefore followed up with a fix to the generator script so this
one is merged and dealt with.

>   bitbake.conf: Modify PACKAGE list ordering to insert -staticdev file
>     before PN

I've replied about this one.

>  qt4: package static libraries correctly to fix warnings

I've held off this one as Martin reported an issue.

Cheers,

Richard




  parent reply	other threads:[~2012-03-14 13:35 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-14  8:33 [PATCH 00/14] Warning Fixes and some Updates Saul Wold
2012-03-14  8:33 ` [PATCH 01/14] owl-video: Fix unpackaged file warning Saul Wold
2012-03-14  8:33 ` [PATCH 02/14] ltp: Package static library in -staticdev Saul Wold
2012-03-14  8:33 ` [PATCH 03/14] quilt: Fix docs packaging warnings Saul Wold
2012-03-14  8:33 ` [PATCH 04/14] autoconf: remove emacs mode files to fix warnings Saul Wold
2012-03-14  8:33 ` [PATCH 05/14] qt4: package static libraries correctly " Saul Wold
2012-03-14 11:39   ` Martin Jansa
2012-03-14 14:44     ` [PATCHv2] " Saul Wold
2012-03-14 14:46       ` Martin Jansa
2012-03-14 14:46     ` [PATCHv3] " Martin Jansa
2012-03-14  8:33 ` [PATCH 06/14] rpm: Package python-rpm static archive correctly Saul Wold
2012-03-14  8:33 ` [PATCH 07/14] python: package static libraries correctly in -staticdev Saul Wold
2012-03-14  8:43   ` Martin Jansa
2012-03-14  8:33 ` [PATCH 08/14] distro_tracking: Updates for manual checks Saul Wold
2012-03-14  8:33 ` [PATCH 09/14] avahi: Update to 0.6.31 Saul Wold
2012-03-14  8:33 ` [PATCH 10/14] man-pages: Update to 3.36 Saul Wold
2012-03-14  8:33 ` [PATCH 11/14] libgalago: Fix package warnings by not packaging autopackage Saul Wold
2012-03-14  8:33 ` [PATCH 12/14] gpgme: fix packaging warnings Saul Wold
2012-03-14 12:49   ` Richard Purdie
2012-03-14  8:33 ` [PATCH 13/14] man: fix configure issue to solve warnings Saul Wold
2012-03-14  8:33 ` [PATCH 14/14] bitbake.conf: Modify PACKAGE list ordering to insert -staticdev file before PN Saul Wold
2012-03-14 12:45   ` Richard Purdie
2012-03-14 13:26 ` Richard Purdie [this message]
2012-03-14 16:09   ` [PATCH 00/14] Warning Fixes and some Updates Saul Wold

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=1331731615.18586.26.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --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