Add libcufile recipe

[mroeschke]

This recipe is based on the libcufile recipe in the nvidia conda channel. This is my first time submitting a recipe.

Note: I noticed the nvidia conda channel recipe doesn't have a test. Is that expected?

Checklist

• Title of this PR is meaningful: e.g. "Adding my_nifty_package", not "updated meta.yaml".
• License file is packaged (see here for an example).
• Source is from official source.
• Package does not vendor other packages. (If a package uses the source of another package, they should be separate packages or the licenses of all packages need to be packaged).
• If static libraries are linked in, the license of the static library is packaged.
• Package does not ship static libraries. If static libraries are needed, follow CFEP-18.
• Build number is 0.
• A tarball (url) rather than a repo (e.g. git_url) is used in your recipe (see here for more details).
• GitHub users listed in the maintainer section have posted a comment confirming they are willing to be listed there.
• When in trouble, please check our knowledge base documentation before pinging a team.

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/libcufile) and found some lint.

Here's what I've got...

For recipes/libcufile:

• The license item is expected in the about section.
• The summary item is expected in the about section.
• The recipe must have some tests.
• Selectors are suggested to take a <two spaces>#<one space>[<expression>] form. See lines [2]

[mroeschke]

cc @jakirkham @adibbley xref #21382

[jakirkham]

Thanks Matthew! 🙏

Had a couple initial suggestions below. Should fix the linter error

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/libcufile) and found some lint.

Here's what I've got...

For recipes/libcufile:

• The summary item is expected in the about section.
• The recipe must have some tests.
• Selectors are suggested to take a <two spaces>#<one space>[<expression>] form. See lines [2]

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/libcufile) and found some lint.

Here's what I've got...

For recipes/libcufile:

• The summary item is expected in the about section.
• The recipe must have some tests.

[jakirkham]

Had a couple suggestions on the recent linter comments that should hopefully address them

[jakirkham]

@adibbley, what do you think about including man in libcufile? Wonder if it is helpful for the end user to have access to the man files for configuration, etc.

[adibbley]

Yes it should be there, it is in the 12.0.0 branch of the original recipe.

[jakirkham]

Suggested change

- man

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/libcufile) and found some lint.

Here's what I've got...

For recipes/libcufile:

• The recipe must have some tests.

[conda-forge-webservices]

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 (recipes/libcufile) and found it was in an excellent condition.

[adibbley]

We don't need this Windows build script, but we do need a linux one to set up the targets directory:
https://github.com/conda-forge/staged-recipes/pull/21723/files#diff-e5bafa1dffa25db6c210c96887404cd7168b4c02772daf9fa5cbedb52b5fbd0e
The pkgconfig name will need to be updated to "cufile*.pc"
And the ppc64le line can be dropped

[conda-forge-webservices]

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 (recipes/libcufile) and found it was in an excellent condition.

[kkraus14]

Not sure if it's already been checked, but does cuFile use the file put here as expected?

[jakirkham]

This is a good question. Will ask

It's possible we would need to set CUFILE_ENV_PATH_JSON for this to work. That could be done with activation script

Suppose a fair question would be whether we want to do this or whether users would rather maintain their own configuration file

[jakirkham]

It looks like we don't need this file. So we dropped it to avoid confusion

We can always revisit this in the feedstock

[jakirkham]

Thanks Keith! 🙏

Agree with moving man to -dev. Have suggested some changes for that

Following up on cufile.json offline

[jakirkham]

This is a good question. Will ask

It's possible we would need to set CUFILE_ENV_PATH_JSON for this to work. That could be done with activation script

Suppose a fair question would be whether we want to do this or whether users would rather maintain their own configuration file

[jakirkham]

Thanks all! 🙏

Let's follow up on anything else in the feedstock 🙂