Closed etiennebacher closed 10 months ago
The easiest way is adding a copy of polars to your universe by adding it to your packages.json. This way the binaries are automatically used when building tidypolars.
Op di 15 aug. 2023 11:42 schreef Etienne Bacher @.***>:
Hi there!
One of my packages (tidypolars https://etiennebacher.r-universe.dev/tidypolars#) has some build failures because I don't know how to specify the repos it should look into when downloading dependencies.
Basically, here's what happens:
- tidypolars depends on polars, which is not on CRAN
- polars has binaries available on R-universe. These binaries have different paths depending on the OS:
- https://rpolars.r-universe.dev for Windows and macOS
- https://rpolars.r-universe.dev/bin/linux/jammy/4.3 for Ubuntu
- in tidypolars DESCRIPTION file, I don't put polars in the Remotes field because Github Actions would try to build from source while there are binaries available, so I simply specify the link above as an additional repo in install.packages() (related lines in my workflow https://github.com/etiennebacher/tidypolars/blob/44dc19d2f48a7f6e561e5ac606f6eaa0a296d170/.github/workflows/check.yml#L39-L47 )
Problem: since polars is not in the Remotes field, the R-universe workflow tries to find it on CRAN and obviously fails https://github.com/r-universe/etiennebacher/actions/runs/5865468592/job/15902455283 .
I think the easiest way to fix the builds for tidypolars on R-universe would be to enable https://rpolars.r-universe.dev (or its Ubuntu variant) when it is looking for dependencies. Is it possible to do so?
I guess that putting polars in Remotes would work as well but it would drastically increase the build time both on my workflows and R-universe workflows since it would need to compile polars from scratch.
Thank you!
— Reply to this email directly, view it on GitHub https://github.com/r-universe-org/help/issues/285, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABUZ76Q3A2Z76A4OWMJ6BDXVM77HANCNFSM6AAAAAA3Q2423Y . You are receiving this because you are subscribed to this thread.Message ID: @.***>
Awesome, it works, thank you
Hi there!
One of my packages (
tidypolars
) has some build failures because I don't know how to specify the repos it should look into when downloading dependencies.Basically, here's what happens:
tidypolars
depends onpolars
, which is not on CRANpolars
has binaries available on R-universe. These binaries have different paths depending on the OS:https://rpolars.r-universe.dev
for Windows and macOShttps://rpolars.r-universe.dev/bin/linux/jammy/4.3
for Ubuntutidypolars
DESCRIPTION file, I don't putpolars
in theRemotes
field because Github Actions would try to build from source while there are binaries available, so I simply specify the link above as an additional repo ininstall.packages()
(related lines in my workflow)Problem: since
polars
is not in theRemotes
field, the R-universe workflow tries to find it on CRAN and obviously fails.I think the easiest way to fix the builds for
tidypolars
on R-universe would be to enablehttps://rpolars.r-universe.dev
(or its Ubuntu variant) when it is looking for dependencies. Is it possible to do so?I guess that putting
polars
inRemotes
would work as well but it would drastically increase the build time both on my workflows and R-universe workflows since it would need to compilepolars
from scratch.Thank you!