| 1 |
On Mon, 2002-01-14 at 09:47, Sebastian Werner wrote: |
| 2 |
> Yes |
| 3 |
> |
| 4 |
> Really cool could be function which updates the system automatically in |
| 5 |
> background... as cronjob or something similar. |
| 6 |
> But for this we need a function which reports errors through sendmail or |
| 7 |
> a mailserver to the admin of this system. It could be cool to update |
| 8 |
> these packages with nearly non priority to get a allways up-to-date |
| 9 |
> system. |
| 10 |
> Only an idea |
| 11 |
Good idea. I was thinking about that too. |
| 12 |
It would require some PGP signing of the ebuilds or it will |
| 13 |
enable, for example, an easy "DNS spoof"-like attack on |
| 14 |
Gentoo based servers. |
| 15 |
Also I think not only errors should be sent to admin, but every |
| 16 |
update activity that is automated. |
| 17 |
|
| 18 |
And, btw, logs for _every_ build stored in /var/tmp would be nice. |
| 19 |
I remember Daniel said that one can always use "script". It's true |
| 20 |
if you know you'll need the log in advance. It can not help |
| 21 |
if build failed and you want to see what did it do at ./configure step. |
| 22 |
And running script before every ebuild is a task I'd like to |
| 23 |
leave to portage to do(well, in fact, "script" will not be the best |
| 24 |
sollution in this case, I guess some redirections when running ebuild.sh |
| 25 |
etc. will do). |
| 26 |
> |
| 27 |
> And yes, it the greatest Linux ever used! |
| 28 |
Sure :-) |
| 29 |
|
| 30 |
|
| 31 |
/Vitaly |
Archives