Closed hmaarrfk closed 1 year ago
conda-forge-webservices[bot]
commented
1 year ago Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
hmaarrfk
commented
1 year ago not sure how to get the bot to make these PRs for us.
Do you think we can use the linux 86 tarball from: https://vulkan.lunarg.com/sdk/home
github-actions[bot]
commented
1 year ago Hi! This is the friendly conda-forge automerge bot!
I considered the following status checks when analyzing this PR:
Thus the PR was passing and merged! Have a great day!
traversaro
commented
1 year ago not sure how to get the bot to make these PRs for us.
Unfortunatly Vulkan-related repos have two kind of tags, development tags named vMAJOR.MINOR.PATH (that from what I understand, should not be packaged) and sdk-related tags, named sdk-MAJOR.MINOR.PATH.TWEAK, see https://github.com/KhronosGroup/Vulkan-Headers#version-tagging-scheme .
To get the autotick-bot to just use the sdk- tags to prepare PRs, it would be ideal to be able to specify a regex or similar as an option to specify which tags should be considered, but I am not an expert of autotick-bot and I never found the time to understand how to implement such feature.
Do you think we can use the linux 86 tarball from: https://vulkan.lunarg.com/sdk/home
The SDK archive is quite big and contains some libraries already packaged in conda-forge (such as jsoncpp). However, I initialite naivily packaged vulkan-headers and vulkan-loader, but later I understood that many other packages are necessary to build a library that uses vulkan, see https://github.com/conda-forge/ogre-next-feedstock/pull/15#issuecomment-1436063662 . As many of this libraries are released together (when the VulkanSDK is released, see https://sdk.lunarg.com/sdk/download/1.3.250.0/linux/config.json for a list) perhaps the easiest way to manage them is to build them has individual packages, but all built my a multi-output feedstock, to ensure that are all built with a compatible set of dependencies. However, I never started working on this to understand if it is actually feasible.
On the other hand, not all libraries released in VulkanSDK have a consistent tag, and fortunatly many of them seems to be fairly good at ABI compatibility, so having a feedstock for each one of them may be the easiest choice.
Checklist
0(if the version changed)conda-smithy(Use the phrase code>@<space/conda-forge-admin, please rerender in a comment in this PR for automated rerendering)