Closed gdevenyi closed 2 years ago
This is normal for new packages because they are built with current global pins. In this case the global pango pin is 1.48. That forces rstudio-desktop
to depend on r-base=4.1.2
because r-base=4.1.3
has already been migrated to pango 1.50. In due course the bot will open a PR here to migrate rstudio
to pango=1.50
and any other active migrations that apply to this feedstock. As those migration PRs are merged here this package will become compatible with more recent r-base
builds.
Is there a development guide for conda-forge or such which describes the moving parts of how all this happens? I have similar confusion regarding openssl 1/3 versions. Thanks!
Things are documented pretty well in https://conda-forge.org/docs/ but didn't really start to understand how things worked until I started maintaining packages myself.
Thanks!
Comment:
Trying to integrate rstudio-desktop into my existing R environment I find it wants to make a lot of changes:
I'm surprised its built against older versions despite being brand new? This also seems to conflict with how its built here: https://github.com/conda-forge/rstudio-feedstock/blob/main/.ci_support/linux_64_r_base4.1.yaml#L13-L14