From: Gary Thomas <gary@mlbassoc.com>
To: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Schizophrenic package management
Date: Tue, 03 Apr 2012 11:52:07 -0600 [thread overview]
Message-ID: <4F7B38C7.6010909@mlbassoc.com> (raw)
Why are both opkg-native and rpm-native needed to build images?
When I asked this previously, I was told that rpm was used because
it has superior dependency tracking. Fair enough (I guess), but
then why is opkg required if I build an image using
PACKAGE_CLASSES = "package_rpm"
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next reply other threads:[~2012-04-03 18:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-03 17:52 Gary Thomas [this message]
2012-04-03 18:03 ` Schizophrenic package management Mark Hatle
2012-04-03 18:07 ` Gary Thomas
2012-04-03 18:17 ` Mark Hatle
2012-04-03 18:21 ` Chris Larson
2012-04-03 18:24 ` Mark Hatle
2012-04-03 18:23 ` Gary Thomas
2012-04-04 10:23 ` Steffen Sledz
2012-04-04 19:01 ` Colin Walters
2012-04-03 18:05 ` Paul Eggleton
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=4F7B38C7.6010909@mlbassoc.com \
--to=gary@mlbassoc.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.