All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: dbus-native --with-x
Date: Wed, 1 Jun 2011 11:48:19 -0500	[thread overview]
Message-ID: <4DE66D53.30505@windriver.com> (raw)
In-Reply-To: <1306945014.2529.113.camel@phil-desktop>

On 6/1/11 11:16 AM, Phil Blundell wrote:
> On Wed, 2011-06-01 at 18:11 +0200, Koen Kooi wrote:
>> Furthermore, rpm-native seems to get built even if you don't select rpm as package format!
> 
> Yeah, it's called in by package.bbclass:
> 
> # rpm is used for the per-file dependency identification
> PACKAGE_DEPENDS += "rpm-native"
> 
> As far as I can tell, the only part that actually gets used is rpmdeps
> and it does seem like there ought to be a more lightweight way of
> obtaining that one binary than building a full rpm and all its
> dependencies.

As you mentioned rpm-native is being used for two reasons.  1 if rpm target
package are selected, it's being used to build, manage and install (rootfs) the
packages.

The other place, where it's always used, is the rpmdeps calculations.

> "rpm-native" -> "bzip2-native"

Above is used as RPM needs bzip2 to compress components that end up in packages.

> "rpm-native" -> "db-native"

Back-end DB is well, Berkley DB.

> "rpm-native" -> "perl-native"

Perl could be disabled if we don't need the perl interfaces to RPM.

> "rpm-native" -> "openssl-native"

OpenSSL is used for signing if I remember correctly.

> "rpm-native" -> "expat-native"

expat is needed for some XML parsing.  (Currently only internally to RPM, but
eventually it's thought this will be used for other purposes.)

> "rpm-native" -> "autoconf-native"
> "rpm-native" -> "automake-native"
> "rpm-native" -> "libtool-native"
> "rpm-native" -> "gnu-config-native"
> "rpm-native" -> "gettext-native"

Above are needed because of configure...

> "rpm-native" -> "python-native"

If we disable python interfaces to RPM, then this can be disabled.

> "rpm-native" -> "acl-native"

ACL's are needed for some filesystem access on rootfs generation.

> "rpm-native" -> "elfutils-native"

elfutils is used for rpmdeps, among other things.

> "rpm-native" -> "libpcre-native"

this is needed for package installation and creation... it's the pattern
recognition.

> "rpm-native" -> "zlib-native"

zlib is needed, similarly to bzip2, in order to compress/extract specific items
that may end up in a package.

> "rpm-native" -> "popt-native"

popt is the command line argument processing used globally within RPM and it's
sub commands.

> "rpm-native" -> "attr-native"

attr is needed similar to the acl stuff, when constructing rootfs components.

--

So in the above, perl and python are really the only items that could be disabled.

--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 16:51 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 [this message]
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
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=4DE66D53.30505@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 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.