Add c-blosc2 2.12.0

[Vertexwahn]

Add c-blosc2 2.12.0

[Vertexwahn]

Need skip-url-stability-check label.

[phaedon]

Does this build rule need the visibility set to public?

in cc_library rule //openvdb:openvdb: target '@@c-blosc2~2.12.0//:c-blosc2' is not visible from target '//openvdb:openvdb'. Check the visibility declaration of the former target if you think the dependency is legitimate

[edit]
Hmm, but this commit doesn't seem to fix the problem:
bazel test ... --registry=https://raw.githubusercontent.com/phaedon/bazel-central-registry/blosc-visibility

[Vertexwahn]

@phaedon You are right visibility = ["//visibility:public"], is missing. Sorry for this. Can you create a version 2.12.0.bcr.1 (i.e. create a folder 2.12.0.bcr.1 - copy the contents from 2.12.0 with the visibility change (as done in your local fork?)

[phaedon]

Will do. So I understand, did my local fork not work because it has to be set up with a different version number?

[Vertexwahn]

@phaedon Depends on the order of registries in your .bazlrc file - e.g.:

common --registry=https://raw.githubusercontent.com/Vertexwahn/bazel-registry/main/ 
common --registry=https://raw.githubusercontent.com/bazelboost/registry/main
common --registry=https://bcr.bazel.build

If I am not wrong this is in an first come first served order. Maybe c-blosc2-2.12.0 was fetched from https://bcr.bazel.build since it was the first registry defined? Nevertheless, it is hidden without visibility- it should definitely be fixed.