Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: dbus-native --with-x
Date: Wed, 1 Jun 2011 11:58:46 -0500	[thread overview]
Message-ID: <4DE66FC6.4030607@windriver.com> (raw)
In-Reply-To: <1306947245.2529.148.camel@phil-desktop>

On 6/1/11 11:54 AM, Phil Blundell wrote:
> On Wed, 2011-06-01 at 11:48 -0500, Mark Hatle wrote:
>> So in the above, perl and python are really the only items that could be disabled.
> 
> Just to be clear, in the list you mentioned, were you talking about the
> usage of rpm-native for rpmdeps, or the usage by package_rpm.bbclass
> itself?

I was talking about rpm-native recipe in general, and how it's used.

rpmdeps requires a good chunk of the rpm infrastructure (even if we don't end up
using rpmbuild or rpm commands during the build..)

> If we can avoid building perl-native and python-native then that
> certainly sounds like a win on its own, though :-)

It "should" be as simple and adding --without-perl and --without-python to the
configuration line...  but I haven't tried it.

--Mark

> p.
> 
> 
> 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core




  reply	other threads:[~2011-06-01 17:01 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 [this message]
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
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=4DE66FC6.4030607@windriver.com \
    --to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox