metrumresearchgroup / pkgr

R package installation and management - reimagined.

https://metrumresearchgroup.github.io/pkgr/docs

39 stars 4 forks source link

Rpath environment variable not propagating from pkgr yaml #383

Closed andersone1 closed 3 years ago

andersone1 commented 3 years ago

@dpastoor @Dreznel

Description:

Checked that ${R_EXE_3_6} returns correct path, but pkgr install did not pick this up.

Screen shot:

Pkgr version:

pkgr v3.0.0-rc1

Metworx version:

Current workaround, hardcode path:

dpastoor commented 3 years ago

I can confirm/reproduce this behavior... but I'm somewhat perplexed. This is an untouched area of code, i've added some verbose logging and it seems the environment variables set are no longer being propogated. I'm not sure if this was due to an upgrade in the go version or what. Under investigation...

dpastoor commented 3 years ago

false alarm - I've determined this is because if an environment variable is just sourced but not exported in the shell session it will not propagate to the pkgr subprocess. We need to update the metworx configuration to properly re-export, therefore this is not a bug in pkgr