First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 4138
Alias:
Product:
Component:
Status: RESOLVED
Resolution: DUPLICATE of bug 11359
Assigned To: Daniel Robbins (RETIRED) <drobbins@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Olav Kolbu <gentoo@kolbu.no>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 4138 depends on: Show dependency tree
Bug 4138 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2002-06-25 07:14 0000
Some packages give you useful information at the end of an install, typically
telling you to remember to do something special to the Apache config or running
some script to set things up etc. However, if you install something that has
lots of dependencies, this can take hours and produce several thousand lines of
output. So chances are slim to none that Joe User will actually read the useful
parts, since it's displayed at the end of each individual install and not at the
end of the whole install chain.

Yes, you can force users to capture stdout/stderr and go through the NN thousand
lines of output afterwards, or you can fix it so that these "nuggets" of
information are remembered and displayed at the end of a run. Even better would
be to also capture this info somewhere semi-structured and have some sort of
extra command/option to call up this information whenever you want.

(Note, I haven't actually made sure that you don't do this already so feel free
to disregard :-)

------- Comment #1 From SpanKY 2002-08-16 18:30:38 0000 -------
*** Bug 4943 has been marked as a duplicate of this bug. ***

------- Comment #2 From Väinö Järvelä 2002-11-13 20:58:17 0000 -------
When i first thought about this, i thought about config file system. It would
say that you have this and this many unread infos in queue. The "info-files"
would be stored as ebuild-##.##.##.info files in a dedicated directory. And when
read with a program like etc-update, you would have an option to delete the file.

This has at least one problem that i can come up right now: If ebuild informs
about errors with einfo (if einfo output is hidden, wouldn't want to read about
error messages through that service.). Like Quake2 -ebuild does (informs if
there are no output support). This could be solved with different command for
outputting errors. Error messages would ofcourse be in different colors and all.

------- Comment #3 From Sam 2002-11-22 09:00:48 0000 -------
Wouldn't it be useful to let portage show all the einfos at the end of an
emerge
'session', like is done with rsync? Einfos are supposed to give important
information, so the user will probably want to see it anyway. So basically it
will be more automatic. I guess portage could log all the einfos to a file for
each session and print the file at the end?

------- Comment #4 From SpanKY 2002-11-23 16:12:03 0000 -------
*** Bug 11137 has been marked as a duplicate of this bug. ***

------- Comment #5 From SpanKY 2002-11-29 11:43:47 0000 -------

*** This bug has been marked as a duplicate of 11359 ***

First Last Prev Next    No search results available      Search page      Enter new bug