All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Volk <f_l_k@t-online.de>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [oe] [meta-oe][PATCH] malcontent: update 1.13.1 -> 1.14.0
Date: Sun, 26 Jul 2026 01:44:57 +0200	[thread overview]
Message-ID: <XM8RIT.IRSXL710O88F2@t-online.de> (raw)
In-Reply-To: <CAMKF1spW8hp-e_TJQvX4v9T5nDx7P7thJ97ZNFXHZNEP6h2PRw@mail.gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=windows-1251; format=flowed, Size: 1091 bytes --]

On Sat, Jul 25 2026 at 08:41:57 -07:00:00, Khem Raj 
<raj.khem@gmail.com> wrote:
> why not inherit gi-docgen class here.

Assuming that the gi-docgen class is intended to make the build of docs 
configurable via the ‘api-documentation’ distro feature, this 
option is not available in malcontent's meson.build. gi-docgen is a 
hard dependency, and the doc build cannot be disabled. Therefore, I 
thought it would be simpler and better reflect what the developer wants 
to simply include `gidocgen-native` as a dependency without any 
conditions.


You mean PV should be included in the recipe name? That's not so easy 
with malcontent. We build it twice. First, without the graphical user 
interface, so we can use it as a dependency for flatpak without 
circular dependencies. Then, a second time, we build the full version 
but manually install only the files for the graphical user interface to 
avoid multiple file providers in `do_rootfs`. Thats why were dependent 
on the recipes being updated together, and that's why PV is included in 
`malcontent.inc`.



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

      reply	other threads:[~2026-07-25 23:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-25  9:45 [meta-oe][PATCH] malcontent: update 1.13.1 -> 1.14.0 Markus Volk
2026-07-25 15:41 ` [oe] " Khem Raj
2026-07-25 23:44   ` Markus Volk [this message]

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=XM8RIT.IRSXL710O88F2@t-online.de \
    --to=f_l_k@t-online.de \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    /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.