| 1 |
Well, there's enotice. |
| 2 |
|
| 3 |
http://dev.gentoo.org/~eldad/ |
| 4 |
|
| 5 |
On 10/11/05, Carlos Silva <r3pek@g.o> wrote: |
| 6 |
> |
| 7 |
> On Tue, 2005-10-11 at 09:18 -0400, Dave Nebinger wrote: |
| 8 |
> > This is probably the fifth time at least that I've been bitten by |
| 9 |
> this... |
| 10 |
> > |
| 11 |
> > Portage is great in that it manages compiles for a bulk of applications |
| 12 |
> > (including dependencies) in one fell swoop. |
| 13 |
> > |
| 14 |
> > Yesterday I emerged gnome - that was it, just gnome, and it took care of |
| 15 |
> the |
| 16 |
> > whole thing soup to nuts. Wahoo, and kudos to all of you who put in the |
| 17 |
> > work. |
| 18 |
> > |
| 19 |
> > But here's my issue... In emerging one of the 101 packages missing on my |
| 20 |
> > system for gnome, a little blurb flew buy that should have caught my |
| 21 |
> > attention, a message posted in the pkg_postinst() message indicating |
| 22 |
> what I |
| 23 |
> > should do now that my installation has completed. |
| 24 |
> > |
| 25 |
> > That's well and good, but as it was one of only 101 other packages, that |
| 26 |
> > message quickly gets lost in the shuffle. |
| 27 |
> > |
| 28 |
> > So here's the enhancement: have portage collect all of these kinds of |
| 29 |
> messages |
| 30 |
> > and display them after all of the emerging has completed. |
| 31 |
> > |
| 32 |
> > So here's my proposed enhancement: Before the call to pkg_postinst(), |
| 33 |
> set a |
| 34 |
> > flag that causes einfo/ewarn/etc. to tee the output generated by the |
| 35 |
> ebuild |
| 36 |
> > to /var/log/portage_postinst.log (or something configurable in make.conf |
| 37 |
> , |
| 38 |
> > whatever). Preface the first generated line with the ${P} so we know |
| 39 |
> what |
| 40 |
> > it's related to. After the pkg_postinst() method completes, clear the |
| 41 |
> flag |
| 42 |
> > and other emerges can carry on as they need to. |
| 43 |
> > |
| 44 |
> > Had this kind of thing been in place, after emerging 101 packages I |
| 45 |
> could go |
| 46 |
> > to the postinst log and see everything that I had to do, including the |
| 47 |
> little |
| 48 |
> > blurb that I had missed before. |
| 49 |
> > |
| 50 |
> > Yes, I know folks are going to say that you can enable portage logging |
| 51 |
> and |
| 52 |
> > look for messages that need to be taken care of. But I just emerged 101 |
| 53 |
> new |
| 54 |
> > packages, have many emerge -ud worlds, etc. resulting in almost 2000 |
| 55 |
> files |
| 56 |
> > out there in /var/log/portage. Talk about the needle in the haystack, |
| 57 |
> > there's not even some specific keywords I could grep on to hit on the |
| 58 |
> > relevant information. |
| 59 |
> > |
| 60 |
> > Understandably I don't know what you all will say about this. It seems |
| 61 |
> like a |
| 62 |
> > great idea to me, and wouldn't appear to come with all the political |
| 63 |
> issues |
| 64 |
> > that the 'extending the ebuild meta data' or some other issues that have |
| 65 |
> come |
| 66 |
> > up recently. |
| 67 |
> > |
| 68 |
> > But I'll leave it to the rest of you to decide... |
| 69 |
> |
| 70 |
> I could be wrong, and if i am, someone from the portage team to correct |
| 71 |
> me, but i think this will come in the next major version of the portage |
| 72 |
> along with the tool elog. |
| 73 |
> |
| 74 |
> -- |
| 75 |
> Carlos "r3pek" Silva |
| 76 |
> Gentoo Developer (kernel/amd64/mobile-phone) |
| 77 |
> |
| 78 |
> |
| 79 |
> -----BEGIN PGP SIGNATURE----- |
| 80 |
> Version: GnuPG v1.4.1-ecc0.1.6 (GNU/Linux) |
| 81 |
> |
| 82 |
> iD8DBQBDS8hAttk+BQds59QRAmA1AJ9B5k3jYh6CnYKdO1hb4oLXBOzjggCffaLD |
| 83 |
> uNSPq9C8xxPpG4bBiH42VC0= |
| 84 |
> =mWCg |
| 85 |
> -----END PGP SIGNATURE----- |
| 86 |
> |
| 87 |
> |
| 88 |
> |
Archives