public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: richard.purdie@linuxfoundation.org
To: Alex Kiernan <alex.kiernan@gmail.com>,
	openembedded-core@lists.openembedded.org
Cc: Alex Kiernan <alexk@zuma.ai>
Subject: Re: [OE-Core][PATCH 1/3] eudev: Convert dependencies to PACKAGECONFIG
Date: Fri, 20 May 2022 09:24:31 +0100	[thread overview]
Message-ID: <5ba8ced312bd0426cdec907f0172834f0823b59f.camel@linuxfoundation.org> (raw)
In-Reply-To: <20220516194915.29231-1-alex.kiernan@gmail.com>

On Mon, 2022-05-16 at 20:49 +0100, Alex Kiernan wrote:
> GObject support was dropped in 252150e181c5 ("src/gudev: remove Gobject
> libudev support."), but some gir support appears to still exist.
> 
> Fill out PACKAGECONFIG options.
> 
> Signed-off-by: Alex Kiernan <alexk@zuma.ai>
> Signed-off-by: Alex Kiernan <alex.kiernan@gmail.com>
> ---
>  meta/recipes-core/udev/eudev_3.2.11.bb | 9 ++++++---
>  1 file changed, 6 insertions(+), 3 deletions(-)
> 
> diff --git a/meta/recipes-core/udev/eudev_3.2.11.bb b/meta/recipes-core/udev/eudev_3.2.11.bb
> index 841039f6d745..0fd1b6ab2283 100644
> --- a/meta/recipes-core/udev/eudev_3.2.11.bb
> +++ b/meta/recipes-core/udev/eudev_3.2.11.bb
> @@ -5,7 +5,7 @@ LICENSE = "GPL-2.0-or-later & LGPL-2.1-or-later"
>  LICENSE:libudev = "LGPL-2.1-or-later"
>  LIC_FILES_CHKSUM = "file://COPYING;md5=751419260aa954499f7abaabaa882bbe"
>  
> -DEPENDS = "glib-2.0 glib-2.0-native gperf-native kmod util-linux"
> +DEPENDS = "gperf-native"
>  
>  PROVIDES = "udev"
>  
> @@ -19,7 +19,7 @@ SRC_URI[sha256sum] = "19847cafec67897da855fde56f9dc7d92e21c50e450aa79068a7e704ed
>  UPSTREAM_CHECK_URI = "https://github.com/eudev-project/eudev/releases"
>  UPSTREAM_CHECK_REGEX = "eudev-(?P<pver>\d+(\.\d+)+)\.tar"
>  
> -inherit autotools update-rc.d qemu pkgconfig features_check manpages
> +inherit autotools update-rc.d qemu pkgconfig features_check manpages gobject-introspection

I like most of what this patch does, cleaning up this kind of thing is
great. I am a bit worried about the gobject-introspection inherit
though as this wasn't there before and brings with it a huge dependency
tree. For something as "core" as udev that is rather sad. Do we really
need it? Should we find a way to disable it by default?

Cheers,

Richard 



  parent reply	other threads:[~2022-05-20  8:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-16 19:49 [OE-Core][PATCH 1/3] eudev: Convert dependencies to PACKAGECONFIG Alex Kiernan
2022-05-16 19:49 ` [OE-Core][PATCH 2/3] eudev: Cleanup redundant configuration Alex Kiernan
2022-05-16 19:49 ` [OE-Core][PATCH 3/3] eudev: Use PACKAGE_BEFORE_PN/${PN} Alex Kiernan
2022-05-20  8:24 ` richard.purdie [this message]
2022-05-20  8:29   ` [OE-Core][PATCH 1/3] eudev: Convert dependencies to PACKAGECONFIG Alex Kiernan

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=5ba8ced312bd0426cdec907f0172834f0823b59f.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=alex.kiernan@gmail.com \
    --cc=alexk@zuma.ai \
    --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