Port all conda recipes to rattler-build

[gforsyth]

Description

Port all condabuild recipes over to use rattler-build instead.

Contributes to rapidsai/build-planning#47

• To satisfy rattler, this changes all the licenses in the pyproject.toml files to the SPDX-compliant Apache-2.0 instead of Apache 2.0

Checklist

• I am familiar with the Contributing Guidelines.
• New or existing tests cover these changes.
• The documentation is up to date with these changes.

[bdice]

Initial comments attached. Please also see my review on UCXX and apply any relevant requests from that PR to this one, too.

[gforsyth]

Computers are the absolute worst.

Despite RAPIDS_CUDA_VERSION being a string, apparently in the process of splitting and extracting the major version, we're getting an integer instead:

       "context": {
        "version": "25.04.00a223",
        "minor_version": "25.04",
        "cuda_version": "11.8",
        "cuda_major": 11,
        "date_string": 250221,
        "head_rev": "1708a669"
      },

rattler-build has a filter for converting from string to int, but not from int to string.
I also can't reproduce this locally.

[gforsyth]

rattler-build has a filter for converting from string to int, but not from int to string.
I also can't reproduce this locally.

Ok, wrapping in quotation marks works. It's very strange that this happens in only some repos, but I'll add "wrap these in strings all the time" to the rattler playbook

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

[gforsyth]

/ok to test

[bdice]

I have only a few leftover comments. However, I think we should merge this soon and work out the remaining items in a follow-up PR wherever we can. Getting this in will help us see any problems, and it'll help with reducing merge conflicts with other work that is going on.

[gforsyth]

/ok to test

[vyasr]

rattler-build has a filter for converting from string to int, but not from int to string.
I also can't reproduce this locally.

Ok, wrapping in quotation marks works. It's very strange that this happens in only some repos, but I'll add "wrap these in strings all the time" to the rattler playbook

Is there a minimal "expected" behavior here that we could capture and write up in a rattler issue?

[gforsyth]

Is there a minimal "expected" behavior here that we could capture and write up in a rattler issue?

I think it might be:

Given that shells have horrendously inconsistent behavior around types, make everything a string unless someone explicitly calls | int

[vyasr]

Is there a minimal "expected" behavior here that we could capture and write up in a rattler issue?

I think it might be:

Given that shells have horrendously inconsistent behavior around types, make everything a string unless someone explicitly calls | int

That seems sensible. Want to write that up as a rattler-build issue?

[gforsyth]

That seems sensible. Want to write that up as a rattler-build issue?

will do

[gforsyth]

rattler-build issue for context types: prefix-dev/rattler-build#1451

[vyasr]

This looks great, thanks Gil! I have some open requests, but nothing worth blocking on so I'm approving now so that you can move ahead. Three requests beyond what I put in-line:

1. Can you go through and resolve all the open discussion threads on this PR? There are a lot, and I want to make sure that we don't miss anything.
2. For any changes that we've decided to punt on for this PR but that we do want to make, could we start documenting them somewhere? I'm fine if we just use something like a google doc (issues feel like extra overhead for how tiny many of the requests are) but it would be good to not lose track of things.
3. In future PRs, could you please avoid force-pushing? We try to avoid those because they decouple the discussion history from the source since the commits vanish.

[gforsyth]

@vyasr thanks for the review -- I'm tracking all of the remaining open requests here: rapidsai/build-planning#47 (comment)

in re: force-pushing, it was a necessary evil because of some unverified commits from one of the lab machines that was continuously blocking CI from running, but I'll avoid it in the future.

[gforsyth]

/merge