From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: John Kehayias <john.kehayias@protonmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: mesa-updates: call for patches
Date: Tue, 31 Oct 2023 09:27:23 -0400 [thread overview]
Message-ID: <87pm0uudl0.fsf@gmail.com> (raw)
In-Reply-To: <878r7jv5yp.fsf@protonmail.com> (John Kehayias's message of "Tue, 31 Oct 2023 03:14:26 +0000")
Hi John,
John Kehayias <john.kehayias@protonmail.com> writes:
> Hi Guix-ers,
>
> Time for another round of Mesa and friends updates! I've been waiting
> for another Mesa release but seems the 23.2 series has stalled out and
> now is a good time before 23.3 or 24. I've been using 23.2.1 for some
> packages locally without issue. I would like to get this branch built
> and then promptly merged, assuming no showstoppers. Actually, probably
> just cherry-pick since it is should just be a few commits and I find
> that cleaner, personally (but happy for advice here).
If you're going to put a branch for it and build it whole, I'd simply
merge it whole after it's done building and hasn't regressed on package
failures or other things.
> There's already a CI build job and I'll submit the request to merge
> for hopefully QA to compare. I will also do some ungrafting. Maxim,
> I'm CC'ing you since you mentioned the core-updates cycle about to
> happen, so if this branch takes some time maybe we'll be better off
> just combining. Let me know. Otherwise I hope to have the branch
> building in a few days and then let it churn.
I'd say go for a branch!
> Here is a list of what has been on my radar and I'll be looking to
> apply on the mesa-updates branch. If there's something I missed and
> you think makes sense here (e.g. lower level graphical/X related
> libraries) please let me know. And yes, I need to make a Mesa team. It
> is on my list!
>
> 1. ungraft libx11 and libxpm
>
> 2. update mesa (23.2.1)
>
> 3. <https://issues.guix.gnu.org/65375> (libepoxy fix for GTK, see <https://issues.guix.gnu.org/64981>)
>
> 4. <https://issues.guix.gnu.org/65155> (mesa vulkan search-paths)
>
> 5. <https://issues.guix.gnu.org/65153> (sdl2 vulkan-loader; and update sdl2?)
>
> 6. <https://issues.guix.gnu.org/64637> (libdrm update; to even newer version now)
>
> 7. <https://issues.guix.gnu.org/66727> (libxkbcommon update)
>
> 8. <https://issues.guix.gnu.org/64639> (pixman update)
>
> 9. submit patch for mesa team
>
> Thanks everyone! And when you see the updates pushed on mesa-updates
> and builds become available, please do test and let me know. Or if
> you'd like to join this team of one, happy to have you on board.
Sounds like a fine plan! Thank you for tackling this!
--
Thanks,
Maxim
next prev parent reply other threads:[~2023-10-31 13:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 3:14 mesa-updates: call for patches John Kehayias
2023-10-31 13:27 ` Maxim Cournoyer [this message]
2023-11-06 4:37 ` John Kehayias
-- strict thread matches above, loose matches on Subject: below --
2023-11-06 4:49 John Kehayias
2023-11-15 5:39 John Kehayias
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=87pm0uudl0.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=guix-devel@gnu.org \
--cc=john.kehayias@protonmail.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.