New package: NNlibCUDA v0.1.0

[JuliaRegistrator]

• Registering package: NNlibCUDA
• Repository: https://github.com/FluxML/NNlibCUDA.jl
• Created by: @DhairyaLGandhi
• Version: v0.1.0
• Commit: 1e08c812902c9ff6da3c0a6ce21bab25d5f0dcd1
• Reviewed by: @DhairyaLGandhi
• Reference: FluxML/NNlibCUDA.jl@1e08c81#commitcomment-49639086

[github-actions]

Your new package pull request met all of the guidelines for auto-merging and is scheduled to be merged when the mandatory waiting period (3 days) has elapsed.

Since you are registering a new package, please make sure that you have read the package naming guidelines: https://julialang.github.io/Pkg.jl/dev/creating-packages/#Package-naming-guidelines-1

---

If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.

[DilumAluthge]

[noblock]

@DhairyaLGandhi @CarloLucibello Is it expected that this package fails to import?

Generally, I recommend that a package is always importable, even if, for example, a CUDA GPU is not available. This is how CUDA.jl works - you can do import CUDA even if a CUDA GPU is not available.

If that is not possible, an alternate approach would be to check for the JULIA_REGISTRYCI_AUTOMERGE environment variable. AutoMerge will set the JULIA_REGISTRYCI_AUTOMERGE environment variable to true. So you can check for that, and skip certain steps if you detect that the package is being imported on AutoMerge.

[DilumAluthge]

[noblock]

Disregard the above comment. Per FluxML/NNlib.jl#300 (comment), the import failures are due to the fact that CUDA 3.0.0 is not yet registered.

[DhairyaLGandhi]

[noblock]

Yeah, that seems to be the case. Should we be able to register a package with unreleased dependencies?

[DilumAluthge]

Blocking this until we make a decision on FluxML/NNlib.jl#300 (comment)

[noblock]

[DhairyaLGandhi]

[noblock]

Could we not block it maybe? We can review the structure but moving it to its repo should be legal no?

[DilumAluthge]

[noblock]

If we change the URL, we need to make sure that all registered versions exist at the new URL, which means that the new URL needs to have all of the same Git trees available.

[CarloLucibello]

[noblock]

If we change the URL, we need to make sure that all registered versions exist at the new URL, which means that the new URL needs to have all of the same Git trees available.

@DilumAluthge this means that if we want to move NNlibCUDA to a separate repo we just push NNlib´s master to the new remote and then remove everything not NNlibCUDA related, right?

[giordano]

Correct

[noblock]

[DilumAluthge]

@DhairyaLGandhi You need a license.

[noblock]