From: "Khem Raj" <raj.khem@gmail.com>
To: openembedded-core@lists.openembedded.org,
Andre McCurdy <armccurdy@gmail.com>
Subject: Re: [OE-core] [PATCH 05/17] kmscube: update to latest commit
Date: Thu, 30 Apr 2020 13:29:41 -0700 [thread overview]
Message-ID: <4f347bfd-c96e-feb0-64fa-52a17a73b2e7@gmail.com> (raw)
In-Reply-To: <CANNYZj-TcGD6QJ1Vnjme4fpZ4uwQB-LAZ-coaSm+jXsjiPHe4g@mail.gmail.com>
On 4/30/20 1:17 PM, Alexander Kanavin wrote:
> On Thu, 30 Apr 2020 at 22:05, Andre McCurdy <armccurdy@gmail.com
> <mailto:armccurdy@gmail.com>> wrote:
>
>
> "No way to understand it" seems a little over dramatic :-) It's
> testing for the availability of a function (gbm_bo_map) within a
> library (libgbm) and then making some code and one of the source files
> conditional on the result of the test.
>
> https://www.gnu.org/software/autoconf/manual/autoconf-2.67/html_node/Libraries.html
>
>
> Andre, I would be more sympathetic to this, if more people would
> actually work on core recipe upgrades, but alas, it seems like it's now
> me alone, despite all the mail that AUH sends to supposed 'maintainers'.
> I have about 60 updates queued [1], and 60 more yet to come, so when I
> see a patch like this (not trivial to rebase, abandoned by original
> submitter, not possible to test), I simply drop it so that progress can
> be made. If you can help, please do.
your effort is appreaciated. Core however has to serve wider usecases,
so that should be considered as well, so ploughing ahead while is good
being mindful about regressing usecases is equally important. All of us
have same challanges.
>
> [1]
> http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=akanavin/package-version-updates
>
> Alex
>
>
>
next prev parent reply other threads:[~2020-04-30 20:29 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 9:57 [PATCH 01/17] libinput: add ptest Alexander Kanavin
2020-04-30 9:58 ` [PATCH 02/17] libinput: update 1.15.2 -> 1.15.5 Alexander Kanavin
2020-04-30 9:58 ` [PATCH 03/17] logrotate: update to 3.16.0 Alexander Kanavin
2020-04-30 9:58 ` [PATCH 04/17] rt-tests: further exclusion of development versions Alexander Kanavin
2020-04-30 9:58 ` [PATCH 05/17] kmscube: update to latest commit Alexander Kanavin
2020-04-30 15:46 ` [OE-core] " Khem Raj
2020-04-30 16:33 ` Alexander Kanavin
2020-04-30 17:33 ` Khem Raj
2020-04-30 20:05 ` Andre McCurdy
2020-04-30 20:17 ` Alexander Kanavin
2020-04-30 20:29 ` Khem Raj [this message]
2020-04-30 20:45 ` Andre McCurdy
2020-04-30 21:01 ` Alexander Kanavin
2020-04-30 9:58 ` [PATCH 06/17] xcb-proto: update to 1.14 Alexander Kanavin
2020-04-30 9:58 ` [PATCH 07/17] libxcb: " Alexander Kanavin
2020-04-30 9:58 ` [PATCH 08/17] mc: update to 4.8.24 Alexander Kanavin
2020-05-02 14:55 ` [OE-core] " Richard Purdie
2020-04-30 9:58 ` [PATCH 09/17] ghostscript: do not hardcode version in SRC_URI Alexander Kanavin
2020-04-30 9:58 ` [PATCH 10/17] ghostscript: update 9.50 -> 9.52 Alexander Kanavin
2020-04-30 15:48 ` [OE-core] " Khem Raj
2020-04-30 17:02 ` Alexander Kanavin
2020-04-30 17:35 ` Khem Raj
2020-04-30 9:58 ` [PATCH 11/17] webkitgtk: update to 2.28.2 Alexander Kanavin
2020-04-30 9:58 ` [PATCH 12/17] python3-gitdb: update to 4.0.4 Alexander Kanavin
2020-04-30 9:58 ` [PATCH 13/17] libevdev: update to 1.9.0 Alexander Kanavin
2020-04-30 9:58 ` [PATCH 14/17] coreutils: update to 8.32 Alexander Kanavin
2020-05-02 14:54 ` [OE-core] " Richard Purdie
2020-05-02 14:56 ` Richard Purdie
2020-04-30 9:58 ` [PATCH 15/17] python3-dbusmock: add recipe from meta-oe Alexander Kanavin
2020-04-30 9:58 ` [PATCH 16/17] glib-2.0: update 2.62.4 -> 2.64.2 Alexander Kanavin
2020-05-02 15:00 ` [OE-core] " Richard Purdie
2020-05-02 18:16 ` Alexander Kanavin
2020-05-02 19:55 ` Alexander Kanavin
2020-04-30 9:58 ` [PATCH 17/17] glib-networking: update to 2.64.2 Alexander Kanavin
2020-05-02 22:20 ` [OE-core] [PATCH 01/17] libinput: add ptest Richard Purdie
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=4f347bfd-c96e-feb0-64fa-52a17a73b2e7@gmail.com \
--to=raj.khem@gmail.com \
--cc=armccurdy@gmail.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