[kdesrc-build] [Bug 394195] Warn if current environment variables do not match with the build of other modules

[Andrew Shark]

https://bugs.kde.org/show_bug.cgi?id=394195

Andrew Shark  changed:

   What|Removed |Added

 Resolution|--- |INTENTIONAL
 Status|REPORTED|RESOLVED
 CC||ash...@linuxcomp.ru

--- Comment #2 from Andrew Shark  ---
Yes, this can be controlled by set-env for those variables you need. But it
already set the needed one. Those the extra - that is your responsibility, not
tool's.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdesrc-build] [Bug 394195] Warn if current environment variables do not match with the build of other modules

[Michael Pyne]

https://bugs.kde.org/show_bug.cgi?id=394195

--- Comment #1 from Michael Pyne  ---
It *could* do this, the infrastructure I would use to implement this (hashing
of option values and persistent data storage) already exist.  The question
would be which env vars to monitor.

*But*, you may want to consider the set-env global option in your
kdesrc-buildrc to ensure that critical environment variables are set by
kdesrc-build itself.  See
https://docs.kde.org/trunk5/en/extragear-utils/kdesrc-build/conf-options-table.html#conf-set-env

-- 
You are receiving this mail because:
You are watching all bug changes.