[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    kdesrc-build messes with environment
From:       Milian Wolff <mail () milianw ! de>
Date:       2019-04-24 12:33:32
Message-ID: 1817268.8GYQMCNuFP () agathebauer
[Download RAW message or body]


Hey all,

for some reason, my `kdesrc-build` uses a different environment than my normal 
shells. I have so far not figured out why that is:

$ env | grep "^PATH="
PATH=/home/milian/.bin:/home/milian/projects/compiled/other/bin:/home/
milian/.bin/kf5:/home/milian/projects/compiled/kf5-dbg/bin:/home/milian/
projects/compiled/other/bin:/home/milian/projects/compiled/kf5/bin:/usr/local/
sbin:/usr/local/bin:/usr/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/
bin/vendor_perl:/usr/bin/core_perl

$ kdesrc-build --run env | grep "^PATH="
PATH=/bin:/home/milian/.bin:/home/milian/projects/compiled/other/bin:/home/
milian/.bin/kf5:/home/milian/projects/compiled/kf5-dbg/bin:/home/milian/
projects/compiled/other/bin:/home/milian/projects/compiled/kf5/bin:/usr/local/
sbin:/usr/local/bin:/usr/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/
bin/vendor_perl:/usr/bin/core_perl

Note how it prepends /bin to PATH, which leads to all kinds of nasty side 
effects for me. I want my PATH to be used as-is, most notably such that some 
of the tools I've built myself get picked up, rather than the versions I have 
available globally in /bin.

Does anyone know where this could come from?

Thanks
-- 
Milian Wolff
mail@milianw.de
http://milianw.de
["signature.asc" (application/pgp-signature)]

[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic