From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] openssl: Move libcrypto to base_libdir
Date: Fri, 10 Feb 2012 13:37:25 +0000 [thread overview]
Message-ID: <1328881046.14363.85.camel@phil-desktop> (raw)
In-Reply-To: <CAMKF1spd_cGhVtd-_ebgUgyMKHFzsB8JhfF0gdByJBeyvr6_9w@mail.gmail.com>
On Thu, 2012-02-09 at 11:54 -0800, Khem Raj wrote:
> eventually I think we will end up with everything being in ${base_libdir} :)
> or we have to make sure that stripped out debug files and standard dev
> libs and headers
> go into /usr
The .debug data does always go into /usr/lib/debug (even on micro).
That path is hardcoded in package.bbclass or some such place and doesn't
depend on ${prefix} or ${libdir}.
> this should be made an option before we go on making these changes IMOs
> I like stuff in /usr and I don't so much care about / and /usr being
> on different partitions
Yes, I agree. As I mentioned the other day, I think having a
DISTRO_FEATURE for "/ usable without /usr mounted" would be a fine idea
and then all this sort of thing can be made conditional on that.
In this particular case I think there's also an underlying issue that,
for most people, having dhcp linked against openssl is probably just not
nececessary. I assume this dependency is because of secure ddns or some
such thing, which is a fine feature but, I suspect, not one that the
majority of OE distros are actually using.
p.
next prev parent reply other threads:[~2012-02-10 13:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-09 18:30 [PATCH] openssl: Move libcrypto to base_libdir Andrei Gherzan
2012-02-09 18:33 ` Phil Blundell
2012-02-09 19:54 ` Khem Raj
2012-02-10 13:37 ` Phil Blundell [this message]
2012-02-09 18:34 ` Saul Wold
-- strict thread matches above, loose matches on Subject: below --
2012-02-10 16:01 Andrei Gherzan
2012-02-21 22:24 ` Saul Wold
2012-02-21 22:40 ` Phil Blundell
2012-02-21 22:53 ` Andrei Gherzan
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=1328881046.14363.85.camel@phil-desktop \
--to=philb@gnu.org \
--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