All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Volk <f_l_k@t-online.de>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: f_l_k@t-online.de, openembedded-devel@lists.openembedded.org
Subject: Re: [oe] [meta-oe][PATCH 1/2] malcontent-ui: add malcontent to RDEPENDS
Date: Mon, 13 May 2024 23:03:47 +0200	[thread overview]
Message-ID: <BUZFDS.4175JRWDQOCF@t-online.de> (raw)
In-Reply-To: <CA+chaQfXGRSwepv6+DS2fYx6ashYnHN0mXx7qc9-XjGcEL-nLw@mail.gmail.com>

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

On Mon, May 13 2024 at 10:30:31 PM +02:00:00, Martin Jansa 
<martin.jansa@gmail.com> wrote:
> If libmalcontent-ui-1.so.1 links with libmalcontent-0.so.0 then this
> should be build-time DEPENDS (and then shlibs code in do_package will
> automatically add malcontent to RDEPENDS.

This error is caused by adding malcontent to the DEPENDS field in 
PACKAGECONFIG like I did in gnome-control-center. After enabling this  
in my build the error occurred.
But in the end this RDPEND is not wrong I guess? I've split the package 
in two and without this RDEPEND it would be possible to install 
libmalcontent-ui without libmalcontent which would then be broken


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

  reply	other threads:[~2024-05-13 21:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-13 20:08 [meta-oe][PATCH 1/2] malcontent-ui: add malcontent to RDEPENDS Markus Volk
2024-05-13 20:08 ` [meta-oe][PATCH 2/2] gnome-control-center: add PACKAGECONFIG for malcontent Markus Volk
2024-05-13 20:30 ` [oe] [meta-oe][PATCH 1/2] malcontent-ui: add malcontent to RDEPENDS Martin Jansa
2024-05-13 21:03   ` Markus Volk [this message]
2024-05-15 15:44     ` Peter Kjellerstedt
2024-05-16 17:58       ` Markus Volk

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=BUZFDS.4175JRWDQOCF@t-online.de \
    --to=f_l_k@t-online.de \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-devel@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.