Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Thomas Devoogdt <thomas@devoogdt.com>
Cc: buildroot@buildroot.org, fontaine.fabrice@gmail.com
Subject: Re: [Buildroot] [PATCH v2] package/libgtk4: add missing direct dependencies
Date: Wed, 4 Nov 2026 23:42:36 +0100	[thread overview]
Message-ID: <auu0yPag0L5mvMrN@windsurf> (raw)
In-Reply-To: <CACXRmJhjkduyOe2sJUJK59H9Fc-4GehP77t9PSHOnEzqYHcWtQ@mail.gmail.com>

On Wed, Nov 04, 2026 at 10:53:04PM +0100, Thomas Devoogdt wrote:

>     I assume you verified that all those dependencies are not just direct
>     dependencies, but are also _mandatory_ dependencies, correct?
> 
> 
> Yes, all packages are direct and mandatory dependencies.
> 
> cairo: [4]https://gitlab.gnome.org/GNOME/gtk/-/blob/4.21.0/meson.build?ref_type
> =tags#L471-473
> harfbuzz: [5]https://gitlab.gnome.org/GNOME/gtk/-/blob/4.21.0/meson.build?
> ref_type=tags#L476-478
> jpeg: [6]https://gitlab.gnome.org/GNOME/gtk/-/blob/4.21.0/meson.build?ref_type=
> tags#L494
> libdrm: [7]https://gitlab.gnome.org/GNOME/gtk/-/blob/4.21.0/meson.build?
> ref_type=tags#L731
> libfribidi: [8]https://gitlab.gnome.org/GNOME/gtk/-/blob/4.21.0/meson.build?
> ref_type=tags#L474-475
> libpng: [9]https://gitlab.gnome.org/GNOME/gtk/-/blob/4.21.0/meson.build?
> ref_type=tags#L492
> tiff: [10]https://gitlab.gnome.org/GNOME/gtk/-/blob/4.21.0/meson.build?ref_type
> =tags#L493
> x11: [11]https://gitlab.gnome.org/GNOME/gtk/-/blob/4.21.0/meson.build?ref_type=
> tags#L606-664

Perfect, thanks for the confirmation!

>     Because for the patch on libgtk3, I think you got this wrong (I'll
>     reply to it separately).
> 
> 
> I will have a look, and also reply separately.

Thanks a lot!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2026-11-04 22:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-31 18:36 [Buildroot] [PATCH v1 1/2] package/libglib2: bump to version 2.90.1 Thomas Devoogdt
2026-10-31 18:36 ` [Buildroot] [PATCH v1 2/2] package/libgtk4: bump to version 4.24.1 Thomas Devoogdt
2026-11-01 16:43   ` Thomas Petazzoni via buildroot
2026-11-02 16:05     ` [Buildroot] [PATCH v2] package/libgtk4: add missing direct dependencies Thomas Devoogdt
2026-11-02 16:05       ` [Buildroot] [PATCH v2] package/libgtk4: bump to version 4.24.1 Thomas Devoogdt
2026-11-04 20:32         ` Thomas Petazzoni via buildroot
2026-11-02 16:05       ` [Buildroot] [PATCH v2] package/libgtk3: add missing direct dependencies Thomas Devoogdt
2026-11-04 20:34         ` Thomas Petazzoni via buildroot
2026-11-04 22:14           ` Thomas Devoogdt
2026-11-04 22:15             ` Thomas Devoogdt
2026-11-04 20:31       ` [Buildroot] [PATCH v2] package/libgtk4: " Thomas Petazzoni via buildroot
2026-11-04 21:53         ` Thomas Devoogdt
2026-11-04 22:42           ` Thomas Petazzoni via buildroot [this message]
2026-11-01 16:39 ` [Buildroot] [PATCH v1 1/2] package/libglib2: bump to version 2.90.1 Thomas Petazzoni via buildroot

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=auu0yPag0L5mvMrN@windsurf \
    --to=buildroot@buildroot.org \
    --cc=fontaine.fabrice@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=thomas@devoogdt.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox