Summary: | app-portage/eix-0.13.3-r1 doesn't honor ~/.eixrc when ran as a postsync hook to emerge --sync | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jeremy Olexa (darkside) (RETIRED) <darkside> |
Component: | New packages | Assignee: | Martin Väth <martin> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | genstef |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Jeremy Olexa (darkside) (RETIRED)
2008-10-27 02:02:38 UTC
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" ;-) |