| 1 |
This is probably the fifth time at least that I've been bitten by this... |
| 2 |
|
| 3 |
Portage is great in that it manages compiles for a bulk of applications |
| 4 |
(including dependencies) in one fell swoop. |
| 5 |
|
| 6 |
Yesterday I emerged gnome - that was it, just gnome, and it took care of the |
| 7 |
whole thing soup to nuts. Wahoo, and kudos to all of you who put in the |
| 8 |
work. |
| 9 |
|
| 10 |
But here's my issue... In emerging one of the 101 packages missing on my |
| 11 |
system for gnome, a little blurb flew buy that should have caught my |
| 12 |
attention, a message posted in the pkg_postinst() message indicating what I |
| 13 |
should do now that my installation has completed. |
| 14 |
|
| 15 |
That's well and good, but as it was one of only 101 other packages, that |
| 16 |
message quickly gets lost in the shuffle. |
| 17 |
|
| 18 |
So here's the enhancement: have portage collect all of these kinds of messages |
| 19 |
and display them after all of the emerging has completed. |
| 20 |
|
| 21 |
So here's my proposed enhancement: Before the call to pkg_postinst(), set a |
| 22 |
flag that causes einfo/ewarn/etc. to tee the output generated by the ebuild |
| 23 |
to /var/log/portage_postinst.log (or something configurable in make.conf, |
| 24 |
whatever). Preface the first generated line with the ${P} so we know what |
| 25 |
it's related to. After the pkg_postinst() method completes, clear the flag |
| 26 |
and other emerges can carry on as they need to. |
| 27 |
|
| 28 |
Had this kind of thing been in place, after emerging 101 packages I could go |
| 29 |
to the postinst log and see everything that I had to do, including the little |
| 30 |
blurb that I had missed before. |
| 31 |
|
| 32 |
Yes, I know folks are going to say that you can enable portage logging and |
| 33 |
look for messages that need to be taken care of. But I just emerged 101 new |
| 34 |
packages, have many emerge -ud worlds, etc. resulting in almost 2000 files |
| 35 |
out there in /var/log/portage. Talk about the needle in the haystack, |
| 36 |
there's not even some specific keywords I could grep on to hit on the |
| 37 |
relevant information. |
| 38 |
|
| 39 |
Understandably I don't know what you all will say about this. It seems like a |
| 40 |
great idea to me, and wouldn't appear to come with all the political issues |
| 41 |
that the 'extending the ebuild meta data' or some other issues that have come |
| 42 |
up recently. |
| 43 |
|
| 44 |
But I'll leave it to the rest of you to decide... |
| 45 |
|
| 46 |
-- |
| 47 |
gentoo-dev@g.o mailing list |
Archives