From: Joshua G Lock <joshua.g.lock@linux.intel.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>,
"Burton, Ross" <ross.burton@intel.com>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: trying to reconcile OE builds with rpm4-format rpm files built on centos 6
Date: Thu, 21 Apr 2016 13:40:48 +0100 [thread overview]
Message-ID: <1461242448.3571.4.camel@linux.intel.com> (raw)
In-Reply-To: <alpine.LFD.2.20.1604210822220.6578@localhost.localdomain>
On Thu, 2016-04-21 at 08:24 -0400, Robert P. J. Day wrote:
> On Thu, 21 Apr 2016, Burton, Ross wrote:
> >
> > On 21 April 2016 at 13:06, Robert P. J. Day <rpjday@crashcourse.ca>
> > wrote:
> > next bit of muttering is, "can we downgrade the OE build to
> > use
> > rpm4-format packages?", which is not a path down which i want
> > to walk.
> >
> >
> > Assuming that the obviously correct option of "build the packages
> > inside OE" really is being written off for mysterious reasons, rpm4
> > was only just removed from oe-core (though depending on what
> > releases you're using you may have never noticed it be added and
> > removed again). So you could just recover that from history
> > (oe-core a6e7a86f1635be9a688c56c25e9d215ea4d2cc84 removed it) and
> > fix it up.
> under the circumstances, that sounds like the simplest approach.
> would we be losing any significant functionality downgrading to rpm4?
> it's not my first choice, but if all that's required is to do basic
> installs and upgrades, i suspect it will work just fine.
On the topic of RPM4 vs. RPM5 you should be able to find more details
in the list archives, I easily found a brief summary by Mark Hatle in
the Yocto Project mailing list archive:
"There are some specific uses of RPM 4 in the YP, but I do caution
against people just using it "because". The RPM 5 version is generally
better suited for the embedded world. (There are been posts on more
reasons on the oe-core lists in the past. But as quick summary --
dynamic architecture support, better cross compilation support, cross-
endian support, more configurable for custom distributions, etc.)"
http://article.gmane.org/gmane.linux.embedded.yocto.general/28654/
We ended up removing RPM4 support because it was clear that it was
broken when using SMART as a package manager and we didn't have the
resources to fix it, nor any objections to its removal.
Some recent examples of the kinds of breakage:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=8968
https://bugzilla.yoctoproject.org/show_bug.cgi?id=8969
Regards,
Joshua
next prev parent reply other threads:[~2016-04-21 12:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-21 12:06 trying to reconcile OE builds with rpm4-format rpm files built on centos 6 Robert P. J. Day
2016-04-21 12:10 ` Burton, Ross
2016-04-21 12:24 ` Robert P. J. Day
2016-04-21 12:40 ` Joshua G Lock [this message]
2016-04-21 13:14 ` Robert P. J. Day
2016-04-21 12:50 ` Robert P. J. Day
2016-04-21 13:16 ` Richard Purdie
2016-04-21 14:25 ` Robert P. J. Day
2016-04-21 15:40 ` Mark Hatle
2016-04-21 15:31 ` Mark Hatle
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=1461242448.3571.4.camel@linux.intel.com \
--to=joshua.g.lock@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
--cc=rpjday@crashcourse.ca \
/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