Bug#1003042: Why aren't non-SDK releases packaged?

2022-01-03 Thread Raul Tambre

Source: vulkan-validationlayers
Version: 1.2.189.0-1.1
Severity: wishlist

It seems that debian/watch only tracks tags starting with "sdk-" and 
intermediate releases aren't packaged.

Are there any reasons besides time and manpower? Would there be a way to assist?

Lack of timely releases in downstream distros such as Debian is a pain point I 
brought up in the LunarG Vulkan 2021 ecosystem survey. My impression was that 
this was due to lack of official releases/tags for intermediate versions, but 
they have got back to me and pointed out that that is not the case. And indeed I 
cannot see any difference between SDK and non-SDK tags besides the SDK ones 
having an official binary release from LunarG.




Bug#1003042: Why aren't non-SDK releases packaged?

2022-01-07 Thread Timo Aaltonen

On 3.1.2022 10.31, Raul Tambre wrote:

Source: vulkan-validationlayers
Version: 1.2.189.0-1.1
Severity: wishlist

It seems that debian/watch only tracks tags starting with "sdk-" and 
intermediate releases aren't packaged.
Are there any reasons besides time and manpower? Would there be a way to 
assist?


Lack of timely releases in downstream distros such as Debian is a pain 
point I brought up in the LunarG Vulkan 2021 ecosystem survey. My 
impression was that this was due to lack of official releases/tags for 
intermediate versions, but they have got back to me and pointed out that 
that is not the case. And indeed I cannot see any difference between SDK 
and non-SDK tags besides the SDK ones having an official binary release 
from LunarG.




Building intermediate versions affect the whole stack of 
spirv-headers/-tools, glslang, vulkan-loader etc. And I don't have the 
time for updating them all each time a minor release is out.



--
t