This is entirely non-obvious as one would assume that any exported env vars are inherited by the runroot() subprocesses. Yet they aren't because we intentionally reset the environment in the bwrap containers with --clearenv (see atlocal.in). It's a common use case, though, so deserves a proper note. You can view, comment on, or merge this pull request online at:
https://github.com/rpm-software-management/rpm/pull/2991 -- Commit Summary -- * Add a note about --setenv to test README -- File Changes -- M tests/README.md (7) -- Patch Links -- https://github.com/rpm-software-management/rpm/pull/2991.patch https://github.com/rpm-software-management/rpm/pull/2991.diff -- Reply to this email directly or view it on GitHub: https://github.com/rpm-software-management/rpm/pull/2991 You are receiving this because you are subscribed to this thread. Message ID: <rpm-software-management/rpm/pull/2...@github.com>
_______________________________________________ Rpm-maint mailing list Rpm-maint@lists.rpm.org http://lists.rpm.org/mailman/listinfo/rpm-maint
