From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Stefan Ott <stefan@ott.net>, Adrian Perez de Castro <aperez@igalia.com>
Cc: Daniel Lang <d.lang@abatec.at>,
Thomas Devoogdt <thomas.devoogdt@barco.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/libgtk3: Remove atk-bridge from .pc file
Date: Sat, 15 Apr 2023 17:27:00 +0200 [thread overview]
Message-ID: <20230415152700.GN2819@scaer> (raw)
In-Reply-To: <20230415151633.GM2819@scaer>
Adrián, All,
+Thomas, +Daniel,
On 2023-04-15 17:16 +0200, Yann E. MORIN spake thusly:
> Adrián, question below also for you. ;-)
[--SNIP--]
> commit log for the patch mentions that atk-bridge requires at-spi2-core
> and at-spi2-atk, which were not packaged in Buildroot back in the time.
> However, we now have both. So: should we drop this patch, and add the
> dependency onto at-spi2-atk (and thus at-spi2-core), now?
OK, I think I have an answer now:
https://patchwork.ozlabs.org/project/buildroot/list/?series=343801
I'll look at that series now...
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-04-15 15:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 22:26 [Buildroot] [PATCH 1/1] package/libgtk3: Remove atk-bridge from .pc file Stefan Ott via buildroot
2023-04-13 14:13 ` Adrian Perez de Castro
2023-04-15 15:16 ` Yann E. MORIN
2023-04-15 15:27 ` Yann E. MORIN [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=20230415152700.GN2819@scaer \
--to=yann.morin.1998@free.fr \
--cc=aperez@igalia.com \
--cc=buildroot@buildroot.org \
--cc=d.lang@abatec.at \
--cc=stefan@ott.net \
--cc=thomas.devoogdt@barco.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