Replies: 5 comments 4 replies
-
Thank you for trying out rix! There currently is no automated system to automatically discover dependencies. I am thinking of using |
Beta Was this translation helpful? Give feedback.
-
Something like:
Doing this would make {renv} an optional dependency, but at the cost of requiring the user to install it manually afterwards. Making renv a hard dependency would make this seamless though. |
Beta Was this translation helpful? Give feedback.
-
Thank you for the clarification, and the pointers. I'm going to have a play about to see what I can come up with. |
Beta Was this translation helpful? Give feedback.
-
As a quick and dirty hack for CRAN packages (only), this is doing what I need outside of rix:
Or shorter:
I'll need to look into how renv deals with non-CRAN dependencies |
Beta Was this translation helpful? Give feedback.
-
Closing this discussion, having understood that this is (rightly) out of scope for the rix package. Nonetheless, the discussion helped me better understand how rix and renv differ, which is really useful. Thank you! |
Beta Was this translation helpful? Give feedback.
-
Thank you for {rix}, an incredibly powerful package!
I may have the workflow confused, but is there any way to recursively discover dependencies for a required project at the time when it's being initialised? I think the current workflow is to manually define the environment in rix::rix(), which generates a .nix file to build it.
Is there any way to build a .nix file by examining the current environment? An example use-case would be cloning a shiny app from github, and then installing all the dependencies in a single line, instead of manually one by one (prompted by the shiny error messages).
Thank you!
Beta Was this translation helpful? Give feedback.
All reactions