Skip to content

Conversation

dlaehnemann
Copy link

Description

This is an attempt at correcting a misleading wording and providing good guidance for the naming of subpackages when using multiple outputs: in a meta.yaml recipe.

For cross-reference, this docs change was noted as being necessary in previous issues:

Also, the previous wording implied that having the top-level name of a recipe repeated in one of the subpackage names. This is exactly the behavior that is cited to cause the unintended side-effects, for example here:

Feel free to further improve the wording, this is mostly meant to get the ball rolling again. Especially since previous efforts to make this name re-use a hard error in conda-build have all gone stale, see for example:

So this is kind of the minimal fix, something like #3314 would be much nicer in the mid-term. And I guess that in the long-term, this should go away if the new recipe format is fully implemented and enforced, see:

Checklist - did you ...

  • Add a file to the news directory (using the template) for the next release's release notes?
  • Add / update necessary tests?
  • Add / update outdated documentation?

@conda-bot
Copy link
Contributor

We require contributors to sign our Contributor License Agreement and we don't have one on file for @dlaehnemann.

In order for us to review and merge your code, please e-sign the Contributor License Agreement PDF. We then need to manually verify your signature, merge the PR (conda/infrastructure#1181), and ping the bot to refresh the PR.

@jezdez
Copy link
Member

jezdez commented Aug 7, 2025

@conda-bot check

@conda-bot conda-bot added the cla-signed [bot] added once the contributor has signed the CLA label Aug 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla-signed [bot] added once the contributor has signed the CLA

Projects

Status: 🆕 New

Development

Successfully merging this pull request may close these issues.

3 participants