Poky Project Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@linux.intel.com>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: poky@yoctoproject.org
Subject: Re: [PULL]Fix moving libtcl8.5.so into tcl-lib.
Date: Sun, 14 Nov 2010 18:52:26 +0000	[thread overview]
Message-ID: <1289760746.1272.5046.camel@rex> (raw)
In-Reply-To: <4CD965EB.9030008@windriver.com>

On Tue, 2010-11-09 at 09:16 -0600, Mark Hatle wrote:
> On 11/8/10 10:52 PM, Lu Jingdong wrote:
> > Saul:
> >
> >      tcl provides only one library named "libtcl8.5.so" and it hasn't
> > libraries named like "libtcl8.5.so.*". So when we use "so.*" in  FILES_
> > ${PN}-lib = "${libdir}/libtcl8.5.so.*", we can't include "libtcl8.5.so"
> > into "tcl-lib" package and we can't get the package "tcl-lib" because it
> > is a empty package.
> >
> >      It doesn't like other libraries. For example, libxcb provides
> > "libxcb-glx.so.0.0.0", "libxcb-glx.so.0" and "libxcb-glx.so". Among of
> > them, "libxcb-glx.so.0" and "libxcb-glx.so" are symbol links of
> > "libxcb-glx.so.0.0.0", so we can use the "so.*" and it includes the
> > following two files("libxcb-glx.so.0.0.0" and "libxcb-glx.so.0"). The
> > file "libxcb-glx.so" is in the "libxcb-dev" package. I am not sure
> > whether "libxcb-glx.so" should in the "libxcb-dev".
> 
> This is likely a check we may want to add to our QA suite.  The rule for which 
> symlinks must be in the run-time package vs a development package is:
> 
> 
> Run-time:
> The actual dynamic library file (duh)
> Symlinks to the dynamic library file with the filename of an SONAME specified by 
> the library file
> 
> 
> Development:
> Any "other" symlinks to the dynamic library NOT referenced by an SONAME
> Any static library files
> Any symlinks to static library files
> Any (related) .la files
> Any (related) .pc files
> Any (related) headers
> 
> 
> It should be fairly simple to validate the run-time, and lack of development 
> components in the run-time package.
> 
> 
> Does anyone know if this validation is already part of the sanity checking, or 
> would this be an enhancement?

I think its all already part of the sanity checks...

Cheers,

Richard



  reply	other threads:[~2010-11-14 18:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-08  7:00 [PULL]Fix moving libtcl8.5.so into tcl-lib Lu Jingdong
2010-11-09  2:20 ` Saul Wold
2010-11-09  4:52   ` Lu Jingdong
2010-11-09 15:16     ` Mark Hatle
2010-11-14 18:52       ` Richard Purdie [this message]
2010-11-10 19:40 ` 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=1289760746.1272.5046.camel@rex \
    --to=rpurdie@linux.intel.com \
    --cc=mark.hatle@windriver.com \
    --cc=poky@yoctoproject.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