Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <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 10:40:29 -0500	[thread overview]
Message-ID: <5718F46D.8010309@windriver.com> (raw)
In-Reply-To: <alpine.LFD.2.20.1604211022280.31857@localhost.localdomain>

On 4/21/16 9:25 AM, Robert P. J. Day wrote:
> On Thu, 21 Apr 2016, Richard Purdie wrote:
> 
>> On Thu, 2016-04-21 at 08:50 -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.
>>>
>>>   just to be clear, if i can dredge up the recipe for rpm_4, i'm
>>> assuming i'd want to specify that i want the "package-management"
>>> image feature, as well as stating:
>>>
>>> PREFERRED_VERSION_rpm = "4.%"
>>> PREFERRED_VERSION_rpm-native = "4.%"
>>>
>>> correct?
>>
>> Just to confuse things further, you could write an OE recipe which
>> took the v4 rpm files from the other system and then simply
>> repackaged them into v5 rpms files. Nothing says you *must* compile
>> from source, the input could be the v4 rpms.
> 
>   great, just what i needed ... yet *another* strategy. in any event,
> can i confirm that if i have the recipe for RPM4, i can use
> PREFERRED_VERSION to use it for the OE build and, later, to install
> RPM4-format rpms built elsewhere?
> 
>   also, *if* i build an image based on RPM4, is it feasible (or even
> possible) to upgrade the whole thing to RPM5 later? i'm not sure i
> even want to think about the grief possibly involved in that.

Due to potential endian and header differences, I don't know.

It was certainly possible in the past to do this (and easy).  But at this point
it may no longer work.

I think this is a question that probably should go to the rpm5-users mailing
list, as they may have more information.

--Mark

>   thanks muchly.
> 
> rday
> 



  reply	other threads:[~2016-04-21 15: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
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 [this message]
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=5718F46D.8010309@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