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/17] Various QA/unpackaged files cleanups
Date: Wed, 06 Jul 2011 09:03:30 +0100 [thread overview]
Message-ID: <1309939410.20015.763.camel@rex> (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.
.la files are an interesting problem. I'm not overly fond of them but
even in this modern age they can help on certain targets like darwin and
they can help with static linking since they have dependency information
that often hasn't been added into the .pc files. We don't often do
either of those things but in general the .la files are pretty harmless.
With regard to the patch series, it just adds .la files to -dev packages
so the only impact is to development images and even there its small.
If you wanted to clean things up, dropping all the binconfig scripts
would IMO be a much more useful effort as those are much more ugly to
handle and bug ridden. At least libtool has some notion of sysroot
support these days!
Cheers,
Richard
next prev parent reply other threads:[~2011-07-06 8:07 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 [this message]
2011-07-06 9:06 ` Phil Blundell
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=1309939410.20015.763.camel@rex \
--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