| 1 |
On Tue, 31 Oct 2006 17:18:03 +0200, Daniel Iliev wrote: |
| 2 |
|
| 3 |
> Let me explain what I'm trying to do. I want to automate "emerge --sync |
| 4 |
> && emerge -DuNv world" with a cron job |
| 5 |
|
| 6 |
I'm not sure automating emerge -u world is good idea. I have a cron task |
| 7 |
that does |
| 8 |
|
| 9 |
emerge --sync |
| 10 |
emerge -upvDN world | mail |
| 11 |
emerge -ufDN world |
| 12 |
|
| 13 |
Then I read the mail and decide on the updates before anything is merged. |
| 14 |
|
| 15 |
> and to receive mails for the |
| 16 |
> portage activities. I really don't need all the gcc output. I only need |
| 17 |
> the portage "info warn error" messages |
| 18 |
|
| 19 |
PORTAGE_ELOG will do this for you. |
| 20 |
|
| 21 |
> in order to know if I have to do "dispatch-conf", |
| 22 |
|
| 23 |
It won't do this, but "find $(portageq config_protect) -name '._cfg*'" |
| 24 |
will. Or you could put it in a script with |
| 25 |
|
| 26 |
if [ "$(find $(portageq config_protect) -name '._cfg*' | wc -l)" != "0" ] |
| 27 |
then |
| 28 |
echo "Run dispatch-conf" |
| 29 |
fi |
| 30 |
|
| 31 |
> if some package has failed and if there is some |
| 32 |
> important note about changes in the structure/functionality of a given |
| 33 |
> package. |
| 34 |
|
| 35 |
PORTAGE_ELOG will tell you that. |
| 36 |
|
| 37 |
|
| 38 |
-- |
| 39 |
Neil Bothwick |
| 40 |
|
| 41 |
Madness takes its toll. Exact change, please. |
Archives