public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: "Matthew Ware (mattware)" <mattware@cisco.com>,
	Alexander Kanavin <alex.kanavin@gmail.com>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>,
	"Elliot Sparling (esparlin)" <esparlin@cisco.com>,
	Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>,
	"adam.duskett@amarulasolutions.com"
	<adam.duskett@amarulasolutions.com>
Subject: Re: [OE-core] RPM 6 in Wrynose
Date: Wed, 11 Mar 2026 20:18:31 +0800	[thread overview]
Message-ID: <f2209b0a-c297-463c-97bc-7139732c498c@windriver.com> (raw)
In-Reply-To: <SN7PR11MB77053FF5985F085C57270866CD46A@SN7PR11MB7705.namprd11.prod.outlook.com>



On 3/11/26 20:00, Matthew Ware (mattware) wrote:
> Hi Alex,
> 
> Fair question! My team are looking at using yocto 6.0 when it's released, and 
> rpm6 has some features we're interested in. If rpm 6 makes it into yocto 6.0 we 

I'm still working on upgrading to 6, here is the latest tmp code:

$ git fetch https://github.com/robertlinux/yocto rbt/rpm_tmp

Currently, it can't provides the pkgconfig files correctly when the pc files are
/usr/share/pkgconfig/, any help is appreciated, for example, help to do more
testing to find the corner cases.

// Robert

> can start taking advantage of those features, and I want to plan for that :). 
> Similar with dnf 5.
> 
> Thanks,
> Matt
> 
> 
> --------------------------------------------------------------------------------
> *From:* Alexander Kanavin <alex.kanavin@gmail.com>
> *Sent:* Tuesday, March 10, 2026 5:26 PM
> *To:* Matthew Ware (mattware) <mattware@cisco.com>
> *Cc:* openembedded-core@lists.openembedded.org <openembedded- 
> core@lists.openembedded.org>; Elliot Sparling (esparlin) <esparlin@cisco.com>; 
> Robert Yang <liezhi.yang@windriver.com>; Mathieu Dubois-Briand <mathieu.dubois- 
> briand@bootlin.com>; adam.duskett@amarulasolutions.com 
> <adam.duskett@amarulasolutions.com>
> *Subject:* Re: [OE-core] RPM 6 in Wrynose
> 
> On Tue, 10 Mar 2026 at 18:24, Matthew Ware (mattware)
> <mattware@cisco.com> wrote:
>  > Also, since we're here: is there any plan to move to DNF 5? I see Wrynose is 
> staying on 4.x, but wondered if there was a plan/aim for DNF 5.
> 
> Yes, there are WIP patches for it too. Adam is working on it.
> 
> I have to ask: can you give us some context? What makes you interested
> in having these versions in Yocto?
> 
> Alex



  reply	other threads:[~2026-03-11 12:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-10 12:16 RPM 6 in Wrynose Matthew Ware (mattware)
2026-03-10 12:50 ` [OE-core] " Alexander Kanavin
2026-03-10 14:09   ` Matthew Ware (mattware)
2026-03-10 17:24     ` Matthew Ware (mattware)
2026-03-10 17:26       ` Alexander Kanavin
2026-03-11  3:19         ` Clayton Casciato
2026-03-11 12:00         ` Matthew Ware (mattware)
2026-03-11 12:18           ` Robert Yang [this message]
2026-03-11 15:42             ` Matthew Ware (mattware)
2026-03-12 11:30               ` Adam Duskett
2026-03-12 14:15               ` Robert Yang
2026-03-12 16:04                 ` Alexander Kanavin

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=f2209b0a-c297-463c-97bc-7139732c498c@windriver.com \
    --to=liezhi.yang@windriver.com \
    --cc=adam.duskett@amarulasolutions.com \
    --cc=alex.kanavin@gmail.com \
    --cc=esparlin@cisco.com \
    --cc=mathieu.dubois-briand@bootlin.com \
    --cc=mattware@cisco.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