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

[DOC] Clarify PREFIX usage in environment variables #5065

Merged
merged 4 commits into from
Nov 20, 2023

Conversation

jakirkham
Copy link
Member

@jakirkham jakirkham commented Nov 10, 2023

Saying <build prefix> now implies BUILD_PREFIX, which isn't the case. AFAIK these have always been constructed based on PREFIX, which is the host environment. Guessing this is just leftover verbiage that needs a refresh.

Also make the same change for LD_RUN_PATH, which has the same issue.

Plus some other lines describing behavior in the prose.


Description

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?

Saying `<build prefix>` now implies `BUILD_PREFIX`, which isn't the
case. AFAIK these have always been constructed based on `PREFIX`, which
is the host environment. Guessing this is just leftover verbiage that
needs a refresh.
@conda-bot conda-bot added the cla-signed [bot] added once the contributor has signed the CLA label Nov 10, 2023
This also uses `$PREFIX`. So correct it too.
@jakirkham jakirkham changed the title [DOC] Clarify LIBRARY_* & SCRIPT use PREFIX [DOC] Clarify PREFIX usage in environment variables Nov 10, 2023
@leofang
Copy link

leofang commented Nov 10, 2023

Thanks, John! Line 135 should be changed to refer to "host" prefix.

FWIW we found the discrepancy between the docs and the code: conda-forge/cupy-feedstock#228 (comment).

@kenodegard kenodegard merged commit 67cc72e into conda:main Nov 20, 2023
9 checks passed
@jakirkham jakirkham deleted the clarify_win_lib_vars branch November 20, 2023 20:05
@jakirkham
Copy link
Member Author

Thanks Ken! 🙏

@jakirkham
Copy link
Member Author

These changes are in the latest docs

@github-actions github-actions bot added the locked [bot] locked due to inactivity label Nov 20, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 20, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
cla-signed [bot] added once the contributor has signed the CLA locked [bot] locked due to inactivity
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

4 participants