-
Notifications
You must be signed in to change notification settings - Fork 12
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
How to determine location of scripts/executables, and set directory where scripts/executable is run #125
Comments
First let's discuss the expected behavior:
Note that for 1, I will always convert to use absolute path. But for 2 i'll have to keep it relative path because it will impact how scripts look like, and therefore trigger unnecessary reruns otherwise. Once we are clear on this, the rest is just coding. As you can see it is more complex due to pipeline behavior, that we cannot just expand everything to use absolute paths. I'll find one peaceful weekend morning to port all path related strings in DSC code to use a formal Python |
@gaow I agree it is important to come up to a consensus on this. |
So @pcarbo you agree with my proposed behavior of 1 & 2 above? |
@gaow Here is a problem with the proposal for 1: relative paths inside the code would only work correctly if the |
Yes you are right. Okey now that we are clear about it i'll find some time to make changes to all path strings in the code. |
When reporting relative paths we will also have to be careful to explain what these paths are relative to. (Or just report absolute paths.) |
Suppose I do
Where does DSC look for the scripts? From which directory are the scripts run?
For guidance it might be helpful to look at argument
knit_root_dir
inrmarkdown::render
because it has to deal with similar issues; seehelp(render)
in R.The text was updated successfully, but these errors were encountered: