public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Ross Burton <Ross.Burton@arm.com>
Cc: "Martin.Jansa@gmail.com" <Martin.Jansa@gmail.com>,
	"Petr Kubizňák" <kubiznak@2n.com>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core][PATCH v5 1/6] gobject-introspection: reduce dependencies
Date: Mon, 15 May 2023 15:40:32 +0000	[thread overview]
Message-ID: <39559677-F466-4605-B918-9B278808F090@arm.com> (raw)
In-Reply-To: <5A51BE7C-AB58-448D-93F2-0AE5EE4C9AA1@arm.com>



> On 15 May 2023, at 14:58, Ross Burton via lists.openembedded.org <ross.burton=arm.com@lists.openembedded.org> wrote:
> g-i-native will *always* be needed as a build dependency, because packages built from git may not have any m4 macros in.

I have a patch, just giving it a soak test.

Ross

      parent reply	other threads:[~2023-05-15 15:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-03 11:06 [OE-core][PATCH v5 1/6] gobject-introspection: reduce dependencies Petr Kubizňák
2023-04-03 11:06 ` [OE-core][PATCH v5 2/6] graphene: add gobject-types PACKAGECONFIG Petr Kubizňák
2023-04-03 11:06 ` [OE-core][PATCH v5 3/6] python3-pygobject: depend on gobject-introspection Petr Kubizňák
2023-04-03 11:06 ` [OE-core][PATCH v5 4/6] gconf: add missing dependencies Petr Kubizňák
2023-04-03 11:06 ` [OE-core][PATCH v5 5/6] webkitgtk: " Petr Kubizňák
2023-04-03 11:06 ` [OE-core][PATCH v5 6/6] libnotify: depend on glib-2.0-native Petr Kubizňák
2023-05-15 11:40 ` [OE-core][PATCH v5 1/6] gobject-introspection: reduce dependencies Martin Jansa
2023-05-15 13:58   ` Ross Burton
2023-05-15 14:49     ` Petr Kubizňák - 2N
2023-05-15 16:43       ` Ross Burton
2023-05-16  8:21         ` Alexander Kanavin
2023-05-15 15:40     ` Ross Burton [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=39559677-F466-4605-B918-9B278808F090@arm.com \
    --to=ross.burton@arm.com \
    --cc=Martin.Jansa@gmail.com \
    --cc=kubiznak@2n.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