Incorrect conda pkg naming

[mike-wendt]

https://anaconda.org/rapidsai-nightly/dask-cuda for conda pkgs uses dask-cuda and I'm pretty sure that a - in the pkg name is not to spec

this is why we have https://anaconda.org/rapidsai-nightly/dask_cudf

can we fix this for the release?

[jakirkham]

Having a - in conda package names generally is acceptable.

It may contain "-", but no spaces.

Though there may be RAPIDS specific conventions that I'm unaware of. So feel free to link relevant docs so I can familiarize myself.

Edit: Here's more info on general conda package naming constraints if it is of interest.

ref: https://docs.conda.io/projects/conda-build/en/latest/resources/define-metadata.html#package-section

[mrocklin]

Dask packages generally follow the `dask-foo` convention

…

On Mon, Mar 18, 2019 at 7:01 AM jakirkham ***@***.***> wrote: Having a - in conda package names generally is acceptable. It may contain "-", but no spaces. Though there may be RAPIDS specific conventions that I'm unaware of. So feel free to link relevant docs so I can familiarize myself. ref: https://docs.conda.io/projects/conda-build/en/latest/resources/define-metadata.html#package-section — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#21 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AASszNN9Yo4nd-gTJmUZVZJK7H5a4Igxks5vX5xBgaJpZM4b5e23> .

[raydouglass]

Agreed. We're going to update all three dask-* to consistently use dashes.