-
-
Notifications
You must be signed in to change notification settings - Fork 274
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
Document support policy around external use of conda-forge-packaged compilers #1998
Comments
I have always considered this a major and supported use case. For a couple of reasons:
From my perspective, the framing here is a little strange. I'd say that conda envs used for regular development on some Python package or application have a much larger audience than using conda envs for building conda-forge packages. In addition, the smaller group of packagers is much better prepared to take an extra preparation step needed for package building and be up-to-date on the recommended ways of doing things. Hence what I'd expect is:
+1. I think any conda-forge-internal-only thing should be opt-in and explicitly enabled. |
It's worth noting that in CUDA 12, the CUDA compiler follows a similar structure |
Where should the content be added?
Somewhere more user-visible than the maintainer docs?
What should be added?
In a recent core discussion, it came up that
I asked:
Since it seems we don't have much that covers someone using (for example)
gcc_linux-64
orclang_osx-64
, and what expectations about continuity, stability, and lack of cf-internals users of such packages can make, I thought I'd open this issue.I don't have a strong opinion either way, but I think we should document what we're willing to support (or not!).
Sidenote: support for our compiler stack (resp. lack thereof) is partially documented in
src/maintainer/infrastructure.rst
(though quite outdated), and the promises we make about this was a point of discussion in #1950Additional information
No response
The text was updated successfully, but these errors were encountered: