Is there an easy way to contribute+collect env var...
# developmentb
bitter-ability-32190
09/08/2022, 2:43 PMIs there an easy way to contribute+collect env vars from dependencies attached to the source? E.g. A
resourcefileLD_LIBRARY_PATHbitter-ability-32190
09/09/2022, 6:18 PMmight want to pursue this. @witty-crayon-22786 this might relate to my earlier idea of sandbox preservation only applyng to "the final process".
These would be injectable (union?) in only "the final process"
w
witty-crayon-22786
09/09/2022, 6:32 PMhm. not sure what you mean.
witty-crayon-22786
09/09/2022, 6:33 PMthere are two aspects of this:
witty-crayon-22786
09/09/2022, 6:34 PMimmutable_inputs — they should likely be used for many more things than they are, hence my suggestion that we should make that API easier to use: https://github.com/pantsbuild/pants/issues/14070#issuecomment-1227645527
witty-crayon-22786
09/09/2022, 6:35 PMenvironment variables to expose libraries — that sounds like a case for either a:
1. typed dependency field to say “oh, this thing that i said was a file/resource? it’s actually a library”
2. different target type to do the same
witty-crayon-22786
09/09/2022, 6:36 PM@fast-nail-55400 and @wide-midnight-78598 would likely have better insight into how to model native dependencies in this case (from Rust/(c)go and c/swift, respectively)
b
bitter-ability-32190
09/09/2022, 6:41 PMModeling it as a plug-in thing might be useful. Similarly, as far as env vars so, adding something to PYTHONPATH, or setting JAVA_HOME could be interesting.