From: Phil Blundell <pb@pbcl.net>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: rpmdeps, was Re: dbus-native --with-x
Date: Thu, 02 Jun 2011 10:18:01 +0100 [thread overview]
Message-ID: <1307006281.2529.169.camel@phil-desktop> (raw)
In-Reply-To: <4DE6AC56.7010308@windriver.com>
On Wed, 2011-06-01 at 16:17 -0500, Mark Hatle wrote:
> I'm not sure if the libraries that RPM uses would even be able to link w/o
> openssl. (I never tried it.) But that will affect people who are using RPM
> packages as signing and validation routines come from openssl.
Sure, but if rpmdeps doesn't need those bits then we could have two
recipes: a heavy one for those people who want rpm packages, and a
lighter one for those who need rpmdeps to make package.bbclass work but
don't otherwise have any requirement for rpm.
p.
next prev parent reply other threads:[~2011-06-02 9:21 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 16:01 dbus-native --with-x Phil Blundell
2011-06-01 16:03 ` Phil Blundell
2011-06-01 16:11 ` Koen Kooi
2011-06-01 16:16 ` Phil Blundell
2011-06-01 16:48 ` Mark Hatle
2011-06-01 16:54 ` Phil Blundell
2011-06-01 16:58 ` Mark Hatle
2011-06-01 17:08 ` Phil Blundell
2011-06-01 18:55 ` rpmdeps, was " Mark Hatle
2011-06-01 19:00 ` Koen Kooi
2011-06-01 21:14 ` Mark Hatle
2011-06-01 20:02 ` Phil Blundell
2011-06-01 21:17 ` Mark Hatle
2011-06-02 9:18 ` Phil Blundell [this message]
2011-06-01 20:22 ` Phil Blundell
2011-06-01 22:00 ` Tom Rini
2011-06-01 22:07 ` Henning Heinold
2011-06-01 22:22 ` Tom Rini
2011-06-01 22:38 ` Mark Hatle
2011-06-02 9:08 ` Phil Blundell
2011-06-02 17:04 ` Tom Rini
2011-06-02 19:21 ` Phil Blundell
2011-06-02 19:29 ` Tom Rini
2011-06-02 7:12 ` Phil Blundell
2011-06-01 16:10 ` Koen Kooi
2011-06-01 16:40 ` Phil Blundell
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=1307006281.2529.169.camel@phil-desktop \
--to=pb@pbcl.net \
--cc=mark.hatle@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 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.