You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Earlier this month, Anaconda [announced](https://www.anaconda.com/blog/changes-to-anacondas-r-channel-support) that they are deprecating the `r` channel bundled in the `defaults` multichannel.
10
+
This decision does _not_ impact R packages in conda-forge, which continue to be available without any changes.
11
+
12
+
<!-- truncate -->
13
+
14
+
The [`@conda-forge/r` team](https://github.com/conda-forge/r-feedstock/blob/7de3342693b3e1e98c2461d5385d8ebcce6b04db/recipe/meta.yaml#L30-L40) currently maintains [4.4K+ feedstocks](https://github.com/search?type=code&q=org%3Aconda-forge+%22-+conda-forge%2Fr%22+path%3Arecipe%2F) for the two latest minor R releases, and will continue to do so. At the time of writing, these are R 4.5 and R 4.4. Older versions are still available but won't receive any updates or rebuilds. When R 4.6 is released, 4.5 will still be maintained and 4.4 will stop receiving updates, and so on.
15
+
16
+
If you have any questions, please do not hesitate to open an issue in the [`r` feedstock](https://github.com/conda-forge/r-feedstock) or in [our Zulip chat instance](https://conda-forge.zulipchat.com/).
Overall: everyone receptive to new compilers. Mike to provide way of keeping host and build prefix separate, even when not cross compiling. This would avoid need for things like "always_include_files" and would facilitate conda-forge keeping their llvmdev recipe as is (for cling usage).
0 commit comments