On Thu, 2019-07-11 at 20:34 -0400, Jeremiah C. Foster wrote:
On Tue, 2019-07-09 at 16:20 -0300, Chris Lamb wrote:
Hi Jeremiah,
I was musing about whether and how environment variables get passed along across various boundaries (container, ssh).
Indeed. If anything, this is what you may encounter problems with, particularly as containers are designed to be, well, not influenced by their outside environment...
I sent a merge request to Matthias for this: https://source.puri.sm/-/ide/project/pureos/infra/make-live/merge_requests/1...
And then, upon further reflection, I merged my own merge request. -_- I know it is ridiculous, but I wanted to test the change and my debspawn runners are going to be fired off shortly and I pull from Gitlab so . . .
- Jeremiah
- Jeremiah
Obvious workarounds (if you need them) that I end up using all the time here are shell "tricks" like explicitly exporting stuff with env(1):
- start-container build-script.sh
- start-container env SOURCE_DATE_EPOCH="${SOURCE_DATE_EPOCH}"
build-script.sh
... and throwing a whole bunch of "echo SDE=$SOURCE_DATE_EPOCH" around is probably the best way to find which barrier is not being crossed.
Best wishes,
PureOS-project mailing list PureOS-project@lists.puri.sm https://lists.puri.sm/listinfo/pureos-project