Re: vulkan suites and multiples maintainers
Vladimir Druzenko <[email protected]>
| Newsgroups | gmane.comp.kde.freebsd |
|---|---|
| Message-ID | <[email protected]> |
28.04.2026 18:25, Max Brazhnikov пишет: > On Sat, 25 Apr 2026 11:27:06 +0200 Olivier Cochard-Labbé wrote: >> The vulkan suite seems to be upgraded all together, but we have 3 different >> maintainers: >> - graphics/spirv-cross : vvd >> - graphics/spirv-headers : Yuri >> - graphics/vulkan-*: kde team > I'm ready to pass graphics/vulkan-* ports over to anyone who is going to take care of them. > I took them for kde@ recently only because Qt6 ports depend on graphics/vulkan-headers. >> So, how does it work when we would like to upgrade it ? :-) >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=294716 >> >> And due to the sensibility of this API, what kind of regression tests >> should we run seriously to test the new version ? > First step would be to build all ports that depend on vulkan ports. > Frankly, I do not know anything about runtime testing. >> I’m using some vkcube and llama.cpp llama-bench on my side, but would like >> to get some input from your side. >> >> Thanks! >> Olivier I created graphics/spirv-cross because it is used by games/lwjgl3 - another my port. I have never encountered any incompatibility with graphics/vulkan-* ports. -- Best regards, Vladimir Druzenko
OpenPGP_0x8006FAABBF942F73.asc
(application/pgp-keys, 1022 B)
-----BEGIN PGP PUBLIC KEY BLOCK----- xjMEZEmcEhYJKwYBBAHaRw8BAQdAzzVRU/u5Oe4kUEFSvaiRoAPwsXMi4uBnfKqF TOIxjaDNI1ZsYWRpbWlyIERydXplbmtvIDx2dmRAZnJlZWJzZC5vcmc+wo8EExYI ADcWIQQJVt5Qnq2dfk5hjMKABvqrv5QvcwUCacM8GwUJCx5LPgIbAwQLCQgHBRUI CQoLBRYCAwEAAAoJEIAG+qu/lC9zh6kBAN/ygnmea43X5OKnYKyPknpHMbmUaU2t TxSu4tnm/zarAP9t0OZWAD4Xkf0jI7pBXzRJ2r0MJkunctLjnoHjMK8WBMKPBBMW CAA3FiEECVbeUJ6tnX5OYYzCgAb6q7+UL3MFAmRJnBIFCQWjmoACGwMECwkIBwUV CAkKCwUWAgMBAAAKCRCABvqrv5Qvc/6nAQC74iaaQn6TfHy4+R350O+QEUv0bzi/ mzxweNtrr/TxTgD/fNpoOLqqGK9Qb0lapq7Qe/6MZKkXiHongSJMgUzPewLOOARk SZwTEgorBgEEAZdVAQUBAQdA+NRiYD7F1MlkHJEX+9uc/ArBgAzI5SKSW1YVlEC4 uH8DAQgHwn4EGBYIACYWIQQJVt5Qnq2dfk5hjMKABvqrv5QvcwUCacM8GwUJCx5L PgIbDAAKCRCABvqrv5Qvc/osAQDgIEyDPHlC2Ypgop3Oo8kpk8cBW5ZIHrmdWba+ 16tOKwEAwj1c/N93P9KvE4ejG1NC6K9TpjZMCR6Na8GLJYkZlQLCfgQYFggAJhYh BAlW3lCerZ1+TmGMwoAG+qu/lC9zBQJkSZwTBQkFo5qAAhsMAAoJEIAG+qu/lC9z 4bgA/jGNXk0cGGKii1lXk55Gwh2EQhC4pLxQe/36TZiR29IBAP40fSUJOJ41IS0d 8k6d5DQ0E9BJuRf+1S5AzsAUz0rmBQ== =dXPi -----END PGP PUBLIC KEY BLOCK-----
OpenPGP_signature.asc
(application/pgp-signature, 236 B)
-----BEGIN PGP SIGNATURE----- wnsEABYIACMWIQQJVt5Qnq2dfk5hjMKABvqrv5QvcwUCafEH7wUDAAAAAAAKCRCABvqrv5Qvc8sn AP4xCkpq9Y3oqO3IP4MrEsEVEwEaT1xgt/++k55x/hwnPAEA1Bzmx98XLI7oVNyaUT74gKAF3YwU McAR4KEiyIv39Ag= =hu0O -----END PGP SIGNATURE-----