Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Minjae Kim" <flowergom@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [dunfell][PATCHv2] libdrm: add libdrm-{nouveau,radeon,intel} to RPROVIDES
Date: Mon, 30 May 2022 00:47:38 -0700	[thread overview]
Message-ID: <953.1653896858036338969@lists.openembedded.org> (raw)
In-Reply-To: <20220529095251.11410-1-flowergom@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 796 bytes --]

@Martin,
I don't know why you think I'm hiding something.
I will use this when installing the rpm package using the dnf tool on the target image such as qemu or raspberrypi.

For example,
There is component A.
It needs libdrm-{nouveau,radeon,intel} packages to work properly.
When this A component rpm package is installed using dnf tool on the actual target image,
the libdrm-{nouveau,radeon,intel} packages cannot install at once if the component A had a libdrm as rdepends.

However, If component A has libdrm-{nouveau,radeon,intel} as rdepends,
When these A component packages are installed using dnf, these packages can also be installed at the same time.

Because libdrm-{nouveau,radeon,intel} is not provided as RPROVIDES, these packages cannot be used as rdepends directly.

[-- Attachment #2: Type: text/html, Size: 928 bytes --]

  parent reply	other threads:[~2022-05-30  7:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-29  9:52 [dunfell][PATCHv2] libdrm: add libdrm-{nouveau,radeon,intel} to RPROVIDES Minjae Kim
2022-05-29 16:15 ` [OE-core] " Martin Jansa
2022-05-30  7:47 ` Minjae Kim [this message]
2022-05-30  8:11   ` Martin Jansa

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=953.1653896858036338969@lists.openembedded.org \
    --to=flowergom@gmail.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