| View previous topic :: View next topic |
| Author |
Message |
locke2053
n00b
Joined: 29 May 2003
Posts: 58
Location: Ohio State University
|
 Posted: Fri Feb 04, 2005 12:48 am Post subject: essential feature missing from portage |
 |
|
Sometimes portage will emerge a package and then beep at you and display some essential command you must run to make things work. These could be telling you that you need to add yourself to a certain group for it to work, or that you need to run some kind of updated script. For people who upgrade every package one at a time, this is fine.
But some people do weekly "emerge -uD world" before they go to bed at night, or they start it remotely. These people miss out on these essential messages. There systems are left with broken software.
The solution? Portage should ask for confirmation "(press enter to continue)" after displaying an important message and before moving on to the next package.
This can't be hard to add, but there will be no way I could have time to implement it in the forseeable future. What do you think? Is this a feature that has been proposed? Should it be done? Can you think of a better solution to this show-stopper problem in portage? |
|
| Back to top |
|
 |
aja
l33t
Joined: 26 Aug 2002
Posts: 705
Location: Edmonton, Canada
|
| Posted: Fri Feb 04, 2005 1:30 am Post subject: Re: essential feature missing from portage |
|
|
| locke2053 wrote: |
But some people do weekly "emerge -uD world" before they go to bed at night, or they start it remotely.
|
| locke2053 wrote: |
Portage should ask for confirmation "(press enter to continue)" after displaying an important message and before moving on to the next package. |
Don't you think a "solution" that hangs the application, waiting for operator input, is inappropriate to solve a "problem" prompted by the absence of an operator?
And, you're using "show stopper" incorrectly. This is arguably not even a bug, much less one that would prevent adoption of the product.
A real solution to the "problem" you describe would be to store such messages to a log that could be reviewed by the system administrator. This is, curiously enough, exactly what happens. |
|
| Back to top |
|
|
John23
n00b
Joined: 15 Dec 2004
Posts: 11
|
| Posted: Fri Feb 04, 2005 3:30 am Post subject: Re: essential feature missing from portage |
|
|
| aja wrote: |
A real solution to the "problem" you describe would be to store such messages to a log that could be reviewed by the system administrator. This is, curiously enough, exactly what happens. |
And which log would that be?
/var/log/emerge.log would seem logical but it captures neither errors nor warnings. |
|
| Back to top |
|
|
Genone
Retired Dev
Joined: 14 Mar 2003
Posts: 9538
Location: beyond the rim
|
| Posted: Fri Feb 04, 2005 5:08 am Post subject: |
|
|
| bug 11359 |
|
| Back to top |
|
|
aja
l33t
Joined: 26 Aug 2002
Posts: 705
Location: Edmonton, Canada
|
| Posted: Fri Feb 04, 2005 7:25 am Post subject: |
|
|
Well, darn. I guess I have to correct myself and apologise to John23 for my excess of sarcasm.
I still disagree that hanging console output is a viable the solution - but I was wrong in implying the problem was already solved.
Coulda sworn that ewarn and einfo events were going to the log...
Anyway, until 2.1 (which will hopefull provide the logging funtionality), the workaround would be to capture emerge's screen output by redirecting it to a file (perhaps using tee to keep the visible output as well), then grep the output.
Something like
| Code: |
emerge <bleah> 2>&1 | tee <logfile>
|
Would work. |
|
| Back to top |
|
|
think4urs11
Bodhisattva
Joined: 25 Jun 2003
Posts: 6659
Location: above the cloud
|
| Posted: Fri Feb 04, 2005 7:51 am Post subject: |
|
|
Hi,
what about using that one in /etc/make.conf?
| Code: | # PORT_LOGDIR is the location where portage will store all the logs it
# creates from each individual merge. They are stored as YYMMDD-$PF.log
# in the directory specified. This is disabled until you enable it by
# providing a directory. Permissions will be modified as needed IF the
# directory exists, otherwise logging will be disabled.
#PORT_LOGDIR=/var/log/portage |
HTH
T.
_________________
Nothing is secure / Security is always a trade-off with usability / Do not assume anything / Trust no-one, nothing / Paranoia is your friend / Think for yourself |
|
| Back to top |
|
|
kallamej
Administrator
Joined: 27 Jun 2003
Posts: 4975
Location: Gothenburg, Sweden
|
|
| Back to top |
|
|
|
Duplicate Threads
