| 1 |
> I think Gentoo should really look at the way ewarn and einfo |
| 2 |
> happen .... they don't do much good at all if you are |
| 3 |
> installing more than one thing. I for one would _love_ to |
| 4 |
> see them all show up at the end of the emerge along with the |
| 5 |
> pkg that they belong with (in the case of long emerges). |
| 6 |
> There are a lot of false bugs (I've registered a couple |
| 7 |
> myself) due to this fact. |
| 8 |
|
| 9 |
I totally agree and have been hoping for a long time that we would have |
| 10 |
something like this for Portage. I think it has been needed for several |
| 11 |
years. I think the only reason it has not been added is because our Portage |
| 12 |
team is inundated with requests for new functionality and thus doesn't |
| 13 |
always have the time to add this kind of stuff (too many distractions.) But |
| 14 |
this seems to be changing as carpaski gets more people up to speed on the |
| 15 |
internals of Portage development, and our APIs become more standardized so |
| 16 |
more people can work on the code simultaneously. |
| 17 |
|
| 18 |
> Most times you have to either a) log the entire build and go |
| 19 |
> through it by hand to figure out if there was crucial info |
| 20 |
> that you missed or b) go back after the fact and manually |
| 21 |
> look at any ebuilds that were installed to see if there are |
| 22 |
> in fact ewarn's or einfo's in them. |
| 23 |
|
| 24 |
Yes, this is a basic usability deficiency in Portage. I envision some kind |
| 25 |
of "info |
| 26 |
Channel" added to Portage. Ebuilds can inject text files into the info |
| 27 |
channel. They will then show up at the end of the merge, or Portage will |
| 28 |
display a message like this after it has run: |
| 29 |
|
| 30 |
There are 3 important package configuration messages you have not yet |
| 31 |
read. |
| 32 |
Type "emerge pkginfo" to read them. |
| 33 |
|
| 34 |
(Just like how it says how many files in /etc need updating.) |
| 35 |
|
| 36 |
> This is kinda sucky, and it's probably been beaten to death |
| 37 |
> before, but here we go again ;) |
| 38 |
|
| 39 |
I know the feeling. Best thing to do would be to contact carpaski and see if |
| 40 |
we can get this on the roadmap. Maybe doing a written specification of how |
| 41 |
this feature should work (like an expansion on what I have above) would be |
| 42 |
helpful. You could also GLEP it. I know you would get lots of support for |
| 43 |
this idea -- someone just needs to sit down and architect a clear, written |
| 44 |
plan to explain how it would all work. For example, what command is used by |
| 45 |
an ebuild to "inject" a text file into the info channel? What emerge option |
| 46 |
is used to view the infochannel messages? What does emerge call ($PAGER?) to |
| 47 |
display the infochannel messages? Once all those little details are agreed |
| 48 |
upon, actual implementation should be relatively easy. |
| 49 |
|
| 50 |
Regards, |
| 51 |
|
| 52 |
Daniel |
| 53 |
|
| 54 |
|
| 55 |
-- |
| 56 |
gentoo-security@g.o mailing list |
Archives