| 1 |
On 9/28/05, Holly Bostick <motub@××××××.nl> wrote: |
| 2 |
> |
| 3 |
> I suppose if you really felt that you wanted to have an emerge of the |
| 4 |
> new packages done automatically, you could always create a script to run |
| 5 |
> esync and mail you the output, then run emerge -uD world after esync |
| 6 |
> completed successfully (doesn't seem much point in using --newuse if |
| 7 |
> you're not going to be there to look at the output), but I prefer to do |
| 8 |
> my emerges manually. |
| 9 |
> |
| 10 |
I'm not really sure automating your updates like that is a really good idea |
| 11 |
especially in light of a few new package layouts that break things. Wouldn't |
| 12 |
that just bite, wake up and, oops the system's broken and I have no idea |
| 13 |
why. |
| 14 |
-Mike |
| 15 |
|
| 16 |
-- |
| 17 |
________________________________ |
| 18 |
Michael E. Crute |
| 19 |
Software Developer |
| 20 |
SoftGroup Development Corporation |
| 21 |
|
| 22 |
Linux, because reboots are for installing hardware. |
| 23 |
"In a world without walls and fences, who needs windows and gates?" |
Archives