| View previous topic :: View next topic |
| Author |
Message |
sridharinfinity
Tux's lil' helper
Joined: 07 Feb 2004
Posts: 84
Location: INDIA
|
 Posted: Wed Jun 09, 2004 1:45 am Post subject: ebuild notifications to user when emerging packages |
 |
|
When I emerge a lot of packages say, in the middle (just after emerging a package), it prints some messages regarding the setup of that package for *full* installtion. The user is supposed to do that.
For example, in nvidia-glx installtion, *we* need to run
| Code: | | # opengl-update nvidia |
and the (nvidia's) ebuild script tells us to do so.
So what if I missed that message just bcoz that the messages are scrolling fast and emerge has started emerging next package in order so that the message got scrolled away -- or what will happen if i shedule the emerging process during night and go to sleep. I should have missed those valuable messages right? I can't sit near the terminal watching over the terminal all during the emerging process!
One solution is to look at the logs (I'm not sure whether every emerge task is logged) but that's too tedious bcoz, we need to search for messages in every packages's log.
We need a better system to allow ebuilds notify the user about pending tasks he has to do *manually* or somesuch. We should come up with a better idea.
Any thoughts?
_________________
Sridhar R
WWW: http://cs.annauniv.edu/~rsridhar |
|
| Back to top |
|
 |
0n0w1c
Apprentice
Joined: 02 Mar 2004
Posts: 273
|
| Posted: Wed Jun 09, 2004 2:02 am Post subject: |
|
|
| You could emerge and run "screen -L" to log the output, then search the single log file. I do agree however, the ebuilds could echo the "todo's" to a text/log file. |
|
| Back to top |
|
|
OhSh33t
Apprentice
Joined: 03 Sep 2003
Posts: 169
Location: South-Seattle Park
|
| Posted: Wed Jun 09, 2004 5:45 am Post subject: |
|
|
Sridharinfinity, trust me. Your beating a dead horse AFAIK. This was fixed along time ago by the following feature below. Just what the doctor ordered. Now you can finally rest while Portage thumps away in the background compiling the goods. 
Right now I've found the best way to capture emerge package messages is by editing /etc/make.conf and either adding or uncommenting this line As root:
| Code: |
PORT_LOGDIR=/var/log/portage
then cd to /var/log and
mkdir portage
|
Thats it. All emerge activity will be captured now for each individual pkg to include those precious configuration hints that your talking about. This can also help you and the dev's debug buggy ebuilds if need be.
But nothing is ever perfect. And you have to take the good with the bad. The only draw back is this DIR can get mighty huge if unadministered as you might imagine. But it only takes a little imagination as how one can deal with such a Portage FEATURE.
HTH's
_________________
JB |
|
| Back to top |
|
|
tomk
Bodhisattva
Joined: 23 Sep 2003
Posts: 7221
Location: Sat in front of my computer
|
|
| Back to top |
|
|
kallamej
Administrator
Joined: 27 Jun 2003
Posts: 4975
Location: Gothenburg, Sweden
|
|
| Back to top |
|
|
|
Duplicate Threads
