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][PATCHv2] libpeas: update 1.36.0 -> 2.0.5
Date: Mon, 16 Dec 2024 22:42:20 +0100 [thread overview]
Message-ID: <KAWLOS.ZXLRPFVITR2B2@t-online.de> (raw)
In-Reply-To: <CAMKF1sr-a7XZyTDfhZdkVxo1ZhLFxLYSm0f28jv65M+0CGsBcw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 981 bytes --]
One additional problem that I see is that some of the older gnome
components like eog or geary dont support libpeas-2 (yet?)
For eog it might be possible to replace it with the more recent rust
app loupe but I guess in case of geary we will be stuck.
Maybe it will be needed to also keep the libpeas-1 recipe for now ?
On Mon, Dec 16 2024 at 01:04:56 PM -08:00:00, Khem Raj
<raj.khem@gmail.com> wrote:
>
>
> On Mon, Dec 16, 2024 at 12:14 PM Markus Volk <f_l_k@t-online.de
> <mailto:f_l_k@t-online.de>> wrote:
>> On Mon, Dec 16 2024 at 09:47:39 AM -08:00:00, Khem Raj
>> <raj.khem@gmail.com <mailto:raj.khem@gmail.com>> wrote:
>>> libpeas seems to be needed by meta-gnome only, so perhaps move this
>>> recipe to meta-gnome is the right thing to do.
>>
>> We could also move gjs to meta-oe because it only pulls in mozjs-128
>> and cairo. Both are also in meta-oe.
>
> Yeah that works too if there are more
> Users of gjs beyond meta-gnome
>>
[-- Attachment #2: Type: text/html, Size: 1796 bytes --]
next prev parent reply other threads:[~2024-12-16 21:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1811A85A00D6A22F.23577@lists.openembedded.org>
2024-12-16 12:34 ` [oe] [meta-oe][PATCHv2] libpeas: update 1.36.0 -> 2.0.5 Markus Volk
2024-12-16 17:47 ` Khem Raj
2024-12-16 20:14 ` Markus Volk
2024-12-16 21:04 ` Khem Raj
2024-12-16 21:42 ` Markus Volk [this message]
2024-12-16 22:32 ` Khem Raj
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=KAWLOS.ZXLRPFVITR2B2@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.