[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug#53581] [PATCH 1/8] gnu: libdrm: Update to 2.4.109.
From: |
phodina |
Subject: |
[bug#53581] [PATCH 1/8] gnu: libdrm: Update to 2.4.109. |
Date: |
Thu, 27 Jan 2022 11:43:13 +0000 |
Hi,
here is a patch set to update the sway window manager to latest version 1.7.
Since it updates wayland packages and libdrm is there a way how to test all the packages which are effected?
Currently I list the affected packages like this:
./pre-inst-env guix refresh --list-dependent <UPDATED PACKAGES>
I can use sed to remove the versions and also remove guix-minimal from the list
sed "s/@[-\.a-zA-Z0-9]* / /g" | sed "s/guix-minimal//g"
Finally I call the build itself
xargs ./pre-inst-env guix build
Since it touches lots of packages I expect it will go to core-updates, right? Should I mark the patches somehow (next time)?
There is package xf86-video-freedreno, but it also fails to build without the patches and by quick check the last commit is ~5yrs old.
Also should I test all the packages to build? I stopped at ungoogled-chromium as that requires a lot of resources and time.
0001-gnu-libdrm-Update-to-2.4.109.patch
Description: Text Data
0002-gnu-wayland-Update-to-1.20.0.patch
Description: Text Data
0006-gnu-cagebreak-Update-to-1.8.3.patch
Description: Text Data
0003-gnu-wayland-protocols-Update-to-1.24.patch
Description: Text Data
0005-gnu-sway-Update-to-1.7.patch
Description: Text Data
0008-gnu-hikari-Update-to-2.3.3.patch
Description: Text Data
0004-gnu-wlroots-Update-to-0.15.0.patch
Description: Text Data
0007-gnu-dwl-Update-to-0.2.2.patch
Description: Text Data
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [bug#53581] [PATCH 1/8] gnu: libdrm: Update to 2.4.109.,
phodina <=