All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Blundell <pb@pbcl.net>
To: akuster808 <akuster808@gmail.com>,
	 openembedded-core@lists.openembedded.org
Cc: Armin Kuster <akuster@mvista.com>
Subject: Re: [PATCH 1/2] ldconfig: add method to extend ldconfig search dirs
Date: Tue, 08 Dec 2015 17:51:55 +0000	[thread overview]
Message-ID: <1449597115.1472.179.camel@pbcl.net> (raw)
In-Reply-To: <56670658.3070109@gmail.com>

On Tue, 2015-12-08 at 08:33 -0800, akuster808 wrote:
> ping
> 
> On 11/11/2015 09:41 AM, Armin Kuster wrote:
> > From: Armin Kuster <akuster@mvista.com>
> > 
> > this provides a method to extend the search path ldconfig-native
> > uses when creating ls.so.cache.
> > 
> > To enable in recipe:
> > 
> > add:
> > inherit ldconfig
> > 
> > LDSOCONF = "/opt/lib"
> > 
> > this will create a ld.so.conf file in work-shared/ldconfig/${PN}/
> > 
> > to create an image with these new search paths included, add to
> > local.conf:
> > 
> > INHERIT += "image-ldconfig"
> > 
> > this will take all the ${PN}/ld.so.conf files and create a single
> > ld.so.conf
> > that will be used by ldconfig-native when building an image.

The problem that you're solving here seems like fundamentally a distro
one.  I remain slightly sceptical that the whole concept of ldconfig
makes a lot of sense for the majority of oe-core users and, for those
for whom it does, I don't entirely understand why it doesn't suffice to
have the packages with unusual requirements install an appropriate file
in /etc/ld.so.conf.d/ and the distro arrange for /etc/ld.so.conf to
include all of those.

So, can you provide a bit more explanation as to why this patch is a
good thing?

p.



  reply	other threads:[~2015-12-08 17:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-11 17:41 [PATCH 0/2] Add ldconfig alt lib search paths Armin Kuster
2015-11-11 17:41 ` [PATCH 1/2] ldconfig: add method to extend ldconfig search dirs Armin Kuster
2015-12-08 16:33   ` akuster808
2015-12-08 17:51     ` Phil Blundell [this message]
     [not found]       ` <56674604.3030900@mvista.com>
2015-12-08 22:34         ` Phil Blundell
     [not found]           ` <566891A3.4040300@mvista.com>
2015-12-09 21:41             ` Phil Blundell
2015-11-11 17:41 ` [PATCH 2/2] ldsoconf: allow extension via local.conf Armin Kuster
2015-11-11 18:39   ` Khem Raj
2015-11-11 19:22     ` akuster808

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=1449597115.1472.179.camel@pbcl.net \
    --to=pb@pbcl.net \
    --cc=akuster808@gmail.com \
    --cc=akuster@mvista.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 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.