From: John Kehayias <john.kehayias@protonmail.com>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: mesa-updates: call for patches
Date: Mon, 06 Nov 2023 04:37:46 +0000 [thread overview]
Message-ID: <87bkc733ag.fsf@protonmail.com> (raw)
In-Reply-To: <87pm0uudl0.fsf@gmail.com>
Hi Maxim and guix-devel,
On Tue, Oct 31, 2023 at 09:27 AM, Maxim Cournoyer wrote:
> Hi John,
>
> John Kehayias <john.kehayias@protonmail.com> writes:
>
[...]
>
> 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.
>
[...]
>
> I'd say go for a branch!
>
Yes, pushed a bunch of changes to mesa-updates after I built up
through mesa locally. Then I hit the rust compiler chain so I decided
to let the CI take over and build everything else too.
Details of changes below, which included some more ungrafting:
>> 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
>>
These are done.
Also, since I didn't realize libx11 means building python, and rust,
and so on, I figured I would ungraft more that was being rebuilt
anyway. So nghttp2 and curl have been ungrafted.
The only more involved change was in ungrafting curl (to keep another
test skip for Hurd), in
<https://git.savannah.gnu.org/cgit/guix.git/commit/?id=00442f15d46cd9d5d02499827946d23426aad0ba&h=mesa-updates>
and then running parallel tests (very nice speed up for building curl
I came across in the documentation!) in
<https://git.savannah.gnu.org/cgit/guix.git/commit/?id=d70f2b788e56545f93dc24238d2617e20fde7460&h=mesa-updates>.
Please do take a look in case I missed something here, but all built
fine locally on x86_64 at least.
>> 2. update mesa (23.2.1)
>>
>> 3. <https://issues.guix.gnu.org/65375> (libepoxy fix for GTK, see
>> <https://issues.guix.gnu.org/64981>)
>>
These are done.
>> 4. <https://issues.guix.gnu.org/65155> (mesa vulkan search-paths)
>>
I don't think this is a correct change as written (search-path should
be in vulkan-loader if I'm understanding what is supposed to happen
here). Anyway, will follow up on that issue and left it out for now.
>> 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)
>>
All these done (sdl2 was also updated to latest version).
>> 9. submit patch for mesa team
>>
But not this one, the easy one :) It will be sent.
>> 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!
Happy to! Substitutes will eventually become available, but there's
quite a few builds to be done. This takes care of some ungrafts and
updates with I hope minimal disruption. I'll be keeping an eye out and
using locally as well. Please test and report, thanks everyone!
John
next prev parent reply other threads:[~2023-11-06 4:38 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
2023-11-06 4:37 ` John Kehayias [this message]
-- 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=87bkc733ag.fsf@protonmail.com \
--to=john.kehayias@protonmail.com \
--cc=guix-devel@gnu.org \
--cc=maxim.cournoyer@gmail.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.