From: Phil Blundell <pb@pbcl.net>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 00/17] Various QA/unpackaged files cleanups
Date: Wed, 06 Jul 2011 10:06:26 +0100 [thread overview]
Message-ID: <1309943187.6337.3.camel@phil-desktop> (raw)
In-Reply-To: <CAP9ODKrdgM9re6WDXWOCCt+g2Jfm7YRewFw4GibTUJBFrOUmVA@mail.gmail.com>
On Tue, 2011-07-05 at 23:59 -0300, Otavio Salvador wrote:
> On Tue, Jul 5, 2011 at 19:51, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > This patch series is for a number of QA/unpackaged files cleanups.
>
> I noticed you have added .la files in some packages. This seems wrong
> and useless. In fact I am making a local patchset to drop them all and
> I have most build working (fixing last things before posting for
> review).
>
> It seems very wrong to depend on .la files for linking and pkg-config
> seems to be the most right solution when possible.
I think Richard's patch to add the .las to the appropriate FILES is a
reasonable one. Whether you actually want the .la files installed or
not is another question, but if your policy is that you don't then I
think the right answer is a global mechanism to suppress them rather
than tinkering with individual recipes. It would probably be fairly
straightforward to make a new class which did something like:
do_purge_la() {
find ${D} -name "*.la" | xargs rm -f
}
addtask purge_la after do_install before do_package do_populate_sysroot
which you could then call in from your DISTRO config as and when
desired.
p.
prev parent reply other threads:[~2011-07-06 9:10 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-05 22:51 [PATCH 00/17] Various QA/unpackaged files cleanups Richard Purdie
2011-07-05 22:51 ` [PATCH 01/17] gcc: Fix unpackaged files warnings, broken symlink and superfluous files Richard Purdie
2011-07-05 22:51 ` [PATCH 02/17] connman: Package unpackaged .la file Richard Purdie
2011-07-06 9:14 ` Phil Blundell
2011-07-06 10:34 ` Richard Purdie
2011-07-05 22:51 ` [PATCH 03/17] tslib: " Richard Purdie
2011-07-05 22:51 ` [PATCH 04/17] btrfs-tools: Fix manpage creation directory Richard Purdie
2011-07-05 22:51 ` [PATCH 05/17] xcb-proto: Package unshipped files, create python-xcbgen package for python xcbgen code Richard Purdie
2011-07-05 22:51 ` [PATCH 06/17] eds-dbus: Package unpackaged files Richard Purdie
2011-07-05 22:51 ` [PATCH 07/17] systemtap: Don't set prefix to a path including so examples get placed in the correct path and packaged correctly Richard Purdie
2011-07-05 22:51 ` [PATCH 08/17] qt4: Package debug source files Richard Purdie
2011-07-05 22:51 ` [PATCH 09/17] telepathy-python: Remove unneeded and unpackaged files Richard Purdie
2011-07-05 22:51 ` [PATCH 10/17] librsvg: Clean up " Richard Purdie
2011-07-05 22:51 ` [PATCH 11/17] gtk-engines: Package " Richard Purdie
2011-07-05 22:51 ` [PATCH 12/17] x11perf: Packaged " Richard Purdie
2011-07-05 22:51 ` [PATCH 13/17] apt: Package " Richard Purdie
2011-07-06 9:17 ` Phil Blundell
2011-07-06 10:25 ` Richard Purdie
2011-07-05 22:51 ` [PATCH 14/17] git: Package up python and gitweb files into appropriate packages Richard Purdie
2011-07-05 22:51 ` [PATCH 15/17] kernelshark/trace-cmd: Clean up QA warnings including fising LDFLAGS issues Richard Purdie
2011-07-06 9:15 ` Phil Blundell
2011-07-05 22:51 ` [PATCH 16/17] opensp: Add unpackaged files Richard Purdie
2011-07-05 22:51 ` [PATCH 17/17] chrpath: Ensure the package respects the docdir variable Richard Purdie
2011-07-06 2:59 ` [PATCH 00/17] Various QA/unpackaged files cleanups Otavio Salvador
2011-07-06 8:03 ` Richard Purdie
2011-07-06 9:06 ` Phil Blundell [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=1309943187.6337.3.camel@phil-desktop \
--to=pb@pbcl.net \
--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