Openembedded Core Discussions
 help / color / mirror / Atom feed
From: ChenQi <Qi.Chen@windriver.com>
To: Phil Blundell <pb@pbcl.net>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] openssl: don't move libcrypto to base_libdir
Date: Fri, 16 Oct 2015 17:33:06 +0800	[thread overview]
Message-ID: <5620C452.8040601@windriver.com> (raw)
In-Reply-To: <1444984136.19532.7.camel@pbcl.net>

On 10/16/2015 04:28 PM, Phil Blundell wrote:
> On Fri, 2015-10-16 at 15:14 +0800, Chen Qi wrote:
>> A patch more than two years ago moves libcrypto from libdir to base_libdir
>> for the reason of /usr split. And I don't think this reason still stands.
> Why not?
>
> p.
>
>
>
>

1) There are a bunch of /usr split patches on the mailing list and they 
are not accepted.
2) It was moved to /lib because dhclient started before mounting the 
local filesystem on sysvinit.
     Now, mounting local filesystem happens before dhclient in sysvinit.

// Qi


      reply	other threads:[~2015-10-16  9:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-16  7:14 [PATCH 0/1] openssl: don't move libcrypto to base_libdir Chen Qi
2015-10-16  7:14 ` [PATCH 1/1] " Chen Qi
2015-10-16  8:28   ` Phil Blundell
2015-10-16  9:33     ` ChenQi [this message]

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=5620C452.8040601@windriver.com \
    --to=qi.chen@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=pb@pbcl.net \
    /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