All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Issues with .list files
Date: Fri, 05 Feb 2010 07:47:11 -0500	[thread overview]
Message-ID: <4B6C134F.9020305@balister.org> (raw)
In-Reply-To: <hkh3ea$jf9$1@ger.gmane.org>

On 02/05/2010 07:37 AM, Koen Kooi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 05-02-10 04:24, Michael Morrell wrote:
>> If I understand the algorithm in package_do_shlibs correctly, each package creates a .list file which is a list of all the shared libraries provided by that package.  It also generates a list of all the libraries that it needs and looks for those in .list files created by other packages so it can create a runtime dependency against that package.
>>
>> The way it looks for .list files is to simply scan all *.list files in the directory.  This has two problems that I can see.
>>
>> First, it is inefficient.  It should only have to look through .list files creates by packages created by bb files which were DEPENDed on by this bb file.
>
> Ehm, no. If it did that you'd get missing shlibs in lots of cases. OE
> won't error out, but you're stabbing users of the packages in the eye
> since they get stuck with the mess.

But it does seem like using a library created by something the recipe 
does not DEPEND on is a problem that should be corrected sooner, rather 
than later.

Philip



  reply	other threads:[~2010-02-05 12:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-05  3:24 Issues with .list files Michael Morrell
2010-02-05 12:37 ` Koen Kooi
2010-02-05 12:47   ` Philip Balister [this message]
2010-02-05 13:50     ` Koen Kooi
2010-02-05 14:14 ` Michael Smith
2010-02-06 11:31 ` Phil Blundell
  -- strict thread matches above, loose matches on Subject: below --
2010-02-05 18:12 Michael Morrell
2010-02-06  7:54 ` Koen Kooi

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=4B6C134F.9020305@balister.org \
    --to=philip@balister.org \
    --cc=openembedded-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.