I have update-eix as a postsync hook when portage does an emerge --sync. When update-eix runs, it doesn't honor ~/.eixrc. My contents of .eixrc are: %% cat .eixrc EXCLUDE_OVERLAY="/home/olexa/sandbox/gentoo-x86" But, it still shows ebuilds from that overlay. When I run update-eix on the command line, it does honor .eixrc when ran as root or my user.
I cannot reproduce this here. Perhaps your cron does not export HOME=/root? (Note: It is important that this variable is exported, not only that it is set shell-internally. update-eix will show in the output a message like "No $HOME found in environment." if it is not exported).
(In reply to comment #1) > I cannot reproduce this here. Perhaps your cron does not export HOME=/root? > (Note: It is important that this variable is exported, not only that it is > set shell-internally. update-eix will show in the output a message like > "No $HOME found in environment." if it is not exported). > Thanks, I will check it out and report back.
hmm, I put HOME="/home/olexa" in my crontabe file because that is where my .eixrc is located, shouldn't that be correct? (It didn't effect anything)
I am not sure (and it may depend on the cron program) whether cron really _exports_ the variables. You can check it by executing the shell script sh -c 'echo $HOME' (it is important to use single quotes and to call a new shell). As a workaround, you can put a shell script to call update-eix instead of inserting update-eix directly into the postsync-hook: #!/bin/sh export HOME=/home/olexa exec update-eix "${@}"
got it, thx for the "tech support" ;-)
