Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: jhuang0 <jackie.huang@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/2] dbus: move libdbus-1.so* to base_libdir
Date: Fri, 21 Jun 2013 13:36:19 +0100	[thread overview]
Message-ID: <1371818179.20823.303.camel@ted> (raw)
In-Reply-To: <51C3B43C.8040707@windriver.com>

On Fri, 2013-06-21 at 10:02 +0800, jhuang0 wrote:
> 
> On 6/20/2013 7:46 PM, Saul Wold wrote:
> > On 06/20/2013 04:14 AM, Richard Purdie wrote:
> >> On Thu, 2013-06-20 at 11:39 +0100, Burton, Ross wrote:
> >>> On 20 June 2013 11:36,  <jackie.huang@windriver.com> wrote:
> >>>> From: Jackie Huang <jackie.huang@windriver.com>
> >>>>
> >>>> move libdbus-1.so* to base_libdir to kill a warning:
> >>>>
> >>>>      WARNING: QA Issue: lib32-consolekit: /lib/security/
> >>>>      pam_ck_connector.so, installed in the base_prefix,
> >>>>      requires a shared library under exec_prefix (/usr):
> >>>>      libdbus-1.so.3 => /usr/lib/libdbus-1.so.3 (0xdead3000)
> >>>>
> >>>> Signed-off-by: Roy.Li <rongqing.li@windriver.com>
> >>>> Signed-off-by: Jackie Huang <jackie.huang@windriver.com>
> >>>
> >>> More and more and more libraries move.  Do we *really* need to support
> >>> split-usr?  Have you audited all of the udev helpers yet?
> >>
> >> I have to admit I'm not happy with the piece by piece approach this is
> >> taking. We're going to end up with nearly everything moving to
> >> base_libdir at this rate. If we're going to do this, I want someone to
> >> come up with a definitive list of what needs to move before any more of
> >> these merge.
> >>
> > And this should be checked with various DISTRO_FEATURES such as pam
> > (enabled/disabled) and systemd (enabled/disabled), not just one
> > variation, please be sure to list what your testing matrix is.
> 
> I tested with DISTRO_FEATURES 'pam' (enabled/disabled) and 'systemd' 
> (enabled/disabled) and WARN_QA = "unsafe-references-in-binaries 
> unsafe-references-in-scripts", and I have sent a v3. If you are agree to 
> merge, please merge the v3 one, thanks!

As I said, I'm not taking any more of these moves until there is a well
thought out analysis/plan. Sorry.

Cheers,

Richard



  reply	other threads:[~2013-06-21 12:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-20 10:36 [PATCH 0/2] consolekit: fix tow QA warnings jackie.huang
2013-06-20 10:36 ` [PATCH 1/2] consolekit: move libck-connector to base_libdir jackie.huang
2013-06-20 11:03   ` jhuang0
2013-06-20 10:36 ` [PATCH 2/2] dbus: move libdbus-1.so* " jackie.huang
2013-06-20 10:39   ` Burton, Ross
2013-06-20 11:14     ` Richard Purdie
2013-06-20 11:27       ` Burton, Ross
2013-06-20 11:46       ` Saul Wold
2013-06-21  2:02         ` jhuang0
2013-06-21 12:36           ` Richard Purdie [this message]
2013-06-27  3:36             ` jhuang0

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=1371818179.20823.303.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=jackie.huang@windriver.com \
    --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