All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: openembedded-devel@openembedded.org
Subject: Re: LEAD_SONAME?
Date: Thu, 27 Mar 2008 10:45:24 -0700	[thread overview]
Message-ID: <20080327174524.GG4938@smtp.west.cox.net> (raw)
In-Reply-To: <1206638031.4514.53.camel@dax.rpnet.com>

On Thu, Mar 27, 2008 at 05:13:51PM +0000, Richard Purdie wrote:
> On Thu, 2008-03-27 at 17:52 +0100, Tom Cooksey wrote:
[snip]
> > > Your options are:
> > > 	- Ignore the warning
> > My prefered option, but only if this is not causing my dissappearing library issue.
> > 
> > > 	- Define a LEAD_SONAME of your primary lib
> > > 	- More finegrained packaging.
> > Do you mean doing having LEAD_SONAME_foo, LEAD_SONAME_bar, etc. ? That
> > could work?
> 
> No, select one e.g. if libfoo is the most "important", LEAD_SONAME =
> "libfoo".

Ah, but what's up with wildcards in the field (ie glib-2.0) ?  Or ones
that say "libfoo.so" (postgresql) or "libfoo.so.1" (uim) ?  People guessing
incorrectly at the value?  Thanks!

-- 
Tom Rini



  reply	other threads:[~2008-03-27 17:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-27 11:17 LEAD_SONAME? Tom Cooksey
2008-03-27 12:30 ` LEAD_SONAME? Tom Cooksey
2008-03-27 14:44 ` LEAD_SONAME? Holger Freyther
2008-03-27 16:52   ` LEAD_SONAME? Tom Cooksey
2008-03-27 17:09     ` LEAD_SONAME? Koen Kooi
2008-03-27 17:13     ` LEAD_SONAME? Richard Purdie
2008-03-27 17:45       ` Tom Rini [this message]
2008-03-28  9:31         ` LEAD_SONAME? Richard Purdie
2008-03-27 17:40     ` LEAD_SONAME? Holger Freyther

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=20080327174524.GG4938@smtp.west.cox.net \
    --to=trini@kernel.crashing.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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.