Versioning of the vulkan-sdk based packages

[Robert Bagdan <kikadf.01%gmail.com@localhost>]

Hi,
I noticed we currently have several packages from the vulkan-sdk,
which has different versions in pkgsrc:

graphics/vulkan-headers: 1.4.349
wip(graphics)/vulkan-loader: 1.4.335.0
graphics/vulkan-tools: 1.4.321.0
parallel/spirv-headers: 1.4.335.0
parallel/spirv-tools: 2025.5

These packages should be kept in sync, as they are closely
interdependent. Although they have independent release cycles,
vulkan-sdk-[version] tags provide a common reference point, so we
should track those.

Note from the readme of vulkan-headers:
“Marked version releases have undergone thorough testing but do not
imply the same quality level as SDK tags. SDK tags follow the
vulkan-sdk-<version>.<patch> format (e.g., vulkan-sdk-1.3.266.0).”

To address this, I introduced a shared vulkan-headers/Makefile.common,
intended to centralize the version to the latest vulkan-sdk-1.4.341.0
for these packages.

I committed the changes to pkgsrc-wip and successfully built the
affected packages locally, including spirv-llvm-translator with the
updated spirv-tools.

However this approach introduces a version downgrade for
vulkan-headers, and - because of the different versioning schema - for
spirv-tools as well. (note, based on SPIRV-Tools.pc:
SPIRV-Tools-vulkan-sdk-1.4.341.0 inside is 2026.1.1)

What would be the recommended way to handle this in pkgsrc?

Is there a mechanism similar to EPOCH in OpenBSD ports?
https://man.openbsd.org/bsd.port.mk#EPOCH

-- 
Regards,
kikadf