Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEA] Split apart multi output conda recipe #11119

Closed
kkraus14 opened this issue Jun 17, 2022 · 4 comments
Closed

[FEA] Split apart multi output conda recipe #11119

kkraus14 opened this issue Jun 17, 2022 · 4 comments
Labels
0 - Backlog In queue waiting for assignment feature request New feature or request

Comments

@kkraus14
Copy link
Collaborator

kkraus14 commented Jun 17, 2022

Is your feature request related to a problem? Please describe.
As far as I can tell / dig up, there's no mechanism in conda-build to allow building only specific outputs of a recipe. With the changes introduced in #10326 I can no longer build just libcudf, but am forced to build the kafka integration library, tests, and example(s) unnecessarily.

Describe the solution you'd like
I'd like to be able to build a libcudf conda package via the conda recipe without having to build a handful of additional unnecessary things.

Describe alternatives you've considered
I can hack the unneeded pieces out of the conda recipe myself, but that's brittle and gross.

@kkraus14 kkraus14 added feature request New feature or request Needs Triage Need team to review and classify labels Jun 17, 2022
@jakirkham
Copy link
Member

Thanks for the feedback Keith 🙏 Agree this is an important use case

Yeah there are probably ways we can influence this like adding environment variables or variants to optionally build subsets of packages

@github-actions
Copy link

This issue has been labeled inactive-30d due to no recent activity in the past 30 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. This issue will be labeled inactive-90d if there is no activity in the next 60 days.

@vyasr
Copy link
Contributor

vyasr commented May 10, 2024

Migrated to rapidsai/build-planning#61

@vyasr vyasr closed this as completed May 10, 2024
@vyasr
Copy link
Contributor

vyasr commented Feb 12, 2025

This will mostly be possible after rapidsai/build-planning#47 is completed, see rapidsai/build-planning#61 (comment) and prefix-dev/rattler-build#1425. The one caveat is that you will have to build the entire dependency tree of a given output, so you can't build libcudf-tests without building libcudf but you can build libcudf without building libcudf.tests. That seems like the right limitation to me though since otherwise you can't reliably satisfy a dependency (e.g. if we had pin_subpackage in place).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0 - Backlog In queue waiting for assignment feature request New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants