[gentoo-dev] Just another portage enhancement idea...

[gentoo-dev] Just another portage enhancement idea...

[Dave Nebinger]

This is probably the fifth time at least that I've been bitten by this...

Portage is great in that it manages compiles for a bulk of applications 
(including dependencies) in one fell swoop.

Yesterday I emerged gnome - that was it, just gnome, and it took care of the 
whole thing soup to nuts.  Wahoo, and kudos to all of you who put in the 
work.

But here's my issue...  In emerging one of the 101 packages missing on my 
system for gnome, a little blurb flew buy that should have caught my 
attention, a message posted in the pkg_postinst() message indicating what I 
should do now that my installation has completed.

That's well and good, but as it was one of only 101 other packages, that 
message quickly gets lost in the shuffle.

So here's the enhancement: have portage collect all of these kinds of messages 
and display them after all of the emerging has completed.

So here's my proposed enhancement: Before the call to pkg_postinst(), set a 
flag that causes einfo/ewarn/etc. to tee the output generated by the ebuild 
to /var/log/portage_postinst.log (or something configurable in make.conf, 
whatever).  Preface the first generated line with the ${P} so we know what 
it's related to.  After the pkg_postinst() method completes, clear the flag 
and other emerges can carry on as they need to.

Had this kind of thing been in place, after emerging 101 packages I could go 
to the postinst log and see everything that I had to do, including the little 
blurb that I had missed before.

Yes, I know folks are going to say that you can enable portage logging and 
look for messages that need to be taken care of.  But I just emerged 101 new 
packages, have many emerge -ud worlds, etc. resulting in almost 2000 files 
out there in /var/log/portage.  Talk about the needle in the haystack, 
there's not even some specific keywords I could grep on to hit on the 
relevant information.

Understandably I don't know what you all will say about this.  It seems like a 
great idea to me, and wouldn't appear to come with all the political issues 
that the 'extending the ebuild meta data' or some other issues that have come 
up recently.

But I'll leave it to the rest of you to decide...

-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Just another portage enhancement idea...

[Marcus D. Hanwell]

[-- Attachment #1: Type: text/plain, Size: 398 bytes --]

On Tuesday 11 October 2005 14:18, Dave Nebinger wrote:
> So here's the enhancement: have portage collect all of these kinds of
> messages and display them after all of the emerging has completed.
>
See bug 11359 - this is an old enhancement request... I would also like to see 
something implemented in portage.
-- 
Gentoo Linux Developer
Scientific Applications | AMD64 | KDE | net-proxy

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] Just another portage enhancement idea...

[Carlos Silva]

[-- Attachment #1: Type: text/plain, Size: 2637 bytes --]

On Tue, 2005-10-11 at 09:18 -0400, Dave Nebinger wrote:
> This is probably the fifth time at least that I've been bitten by this...
> 
> Portage is great in that it manages compiles for a bulk of applications 
> (including dependencies) in one fell swoop.
> 
> Yesterday I emerged gnome - that was it, just gnome, and it took care of the 
> whole thing soup to nuts.  Wahoo, and kudos to all of you who put in the 
> work.
> 
> But here's my issue...  In emerging one of the 101 packages missing on my 
> system for gnome, a little blurb flew buy that should have caught my 
> attention, a message posted in the pkg_postinst() message indicating what I 
> should do now that my installation has completed.
> 
> That's well and good, but as it was one of only 101 other packages, that 
> message quickly gets lost in the shuffle.
> 
> So here's the enhancement: have portage collect all of these kinds of messages 
> and display them after all of the emerging has completed.
> 
> So here's my proposed enhancement: Before the call to pkg_postinst(), set a 
> flag that causes einfo/ewarn/etc. to tee the output generated by the ebuild 
> to /var/log/portage_postinst.log (or something configurable in make.conf, 
> whatever).  Preface the first generated line with the ${P} so we know what 
> it's related to.  After the pkg_postinst() method completes, clear the flag 
> and other emerges can carry on as they need to.
> 
> Had this kind of thing been in place, after emerging 101 packages I could go 
> to the postinst log and see everything that I had to do, including the little 
> blurb that I had missed before.
> 
> Yes, I know folks are going to say that you can enable portage logging and 
> look for messages that need to be taken care of.  But I just emerged 101 new 
> packages, have many emerge -ud worlds, etc. resulting in almost 2000 files 
> out there in /var/log/portage.  Talk about the needle in the haystack, 
> there's not even some specific keywords I could grep on to hit on the 
> relevant information.
> 
> Understandably I don't know what you all will say about this.  It seems like a 
> great idea to me, and wouldn't appear to come with all the political issues 
> that the 'extending the ebuild meta data' or some other issues that have come 
> up recently.
> 
> But I'll leave it to the rest of you to decide...

I could be wrong, and if i am, someone from the portage team to correct
me, but i think this will come in the next major version of the portage
along with the tool elog.

-- 
Carlos "r3pek" Silva
Gentoo Developer (kernel/amd64/mobile-phone)

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-dev] Just another portage enhancement idea...

[José Carlos Cruz Costa]

[-- Attachment #1: Type: text/plain, Size: 3012 bytes --]

Well, there's enotice.

http://dev.gentoo.org/~eldad/

On 10/11/05, Carlos Silva <r3pek@gentoo.org> wrote:
>
> On Tue, 2005-10-11 at 09:18 -0400, Dave Nebinger wrote:
> > This is probably the fifth time at least that I've been bitten by
> this...
> >
> > Portage is great in that it manages compiles for a bulk of applications
> > (including dependencies) in one fell swoop.
> >
> > Yesterday I emerged gnome - that was it, just gnome, and it took care of
> the
> > whole thing soup to nuts. Wahoo, and kudos to all of you who put in the
> > work.
> >
> > But here's my issue... In emerging one of the 101 packages missing on my
> > system for gnome, a little blurb flew buy that should have caught my
> > attention, a message posted in the pkg_postinst() message indicating
> what I
> > should do now that my installation has completed.
> >
> > That's well and good, but as it was one of only 101 other packages, that
> > message quickly gets lost in the shuffle.
> >
> > So here's the enhancement: have portage collect all of these kinds of
> messages
> > and display them after all of the emerging has completed.
> >
> > So here's my proposed enhancement: Before the call to pkg_postinst(),
> set a
> > flag that causes einfo/ewarn/etc. to tee the output generated by the
> ebuild
> > to /var/log/portage_postinst.log (or something configurable in make.conf
> ,
> > whatever). Preface the first generated line with the ${P} so we know
> what
> > it's related to. After the pkg_postinst() method completes, clear the
> flag
> > and other emerges can carry on as they need to.
> >
> > Had this kind of thing been in place, after emerging 101 packages I
> could go
> > to the postinst log and see everything that I had to do, including the
> little
> > blurb that I had missed before.
> >
> > Yes, I know folks are going to say that you can enable portage logging
> and
> > look for messages that need to be taken care of. But I just emerged 101
> new
> > packages, have many emerge -ud worlds, etc. resulting in almost 2000
> files
> > out there in /var/log/portage. Talk about the needle in the haystack,
> > there's not even some specific keywords I could grep on to hit on the
> > relevant information.
> >
> > Understandably I don't know what you all will say about this. It seems
> like a
> > great idea to me, and wouldn't appear to come with all the political
> issues
> > that the 'extending the ebuild meta data' or some other issues that have
> come
> > up recently.
> >
> > But I'll leave it to the rest of you to decide...
>
> I could be wrong, and if i am, someone from the portage team to correct
> me, but i think this will come in the next major version of the portage
> along with the tool elog.
>
> --
> Carlos "r3pek" Silva
> Gentoo Developer (kernel/amd64/mobile-phone)
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1-ecc0.1.6 (GNU/Linux)
>
> iD8DBQBDS8hAttk+BQds59QRAmA1AJ9B5k3jYh6CnYKdO1hb4oLXBOzjggCffaLD
> uNSPq9C8xxPpG4bBiH42VC0=
> =mWCg
> -----END PGP SIGNATURE-----
>
>
>

[-- Attachment #2: Type: text/html, Size: 3599 bytes --]

Re: [gentoo-dev] Just another portage enhancement idea...

[Kevin F. Quinn]

On 11/10/2005 9:18:41, Dave Nebinger (dnebinger@joat.com) wrote:
> This is probably the fifth time at least that I've been bitten by this...

https://bugs.gentoo.org/show_bug.cgi?id=11359
[NEW FEATURE] pkg_postinst/pkg_preinst ewarn/einfo logging


-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Just another portage enhancement idea...

[Alec Joseph Warner]

FYI elog is implemented in CVS ( 2.1 ).  When it will be released is 
anyone's guess.

Kevin F. Quinn wrote:
> On 11/10/2005 9:18:41, Dave Nebinger (dnebinger@joat.com) wrote:
> 
>>This is probably the fifth time at least that I've been bitten by this...
> 
> 
> https://bugs.gentoo.org/show_bug.cgi?id=11359
> [NEW FEATURE] pkg_postinst/pkg_preinst ewarn/einfo logging
> 
> 
-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Just another portage enhancement idea...

[Marius Mauch]

[-- Attachment #1: Type: text/plain, Size: 477 bytes --]

On Tue, 11 Oct 2005 17:00:56 +0000
Alec Joseph Warner <warnera6@egr.msu.edu> wrote:

> FYI elog is implemented in CVS ( 2.1 ).  When it will be released is 
> anyone's guess.

2.1? probably never, but elog will almost certainly be backported to
the 2.0 branch.

Marius

-- 
Public Key at http://www.genone.de/info/gpg-key.pub

In the beginning, there was nothing. And God said, 'Let there be
Light.' And there was still nothing, but you could see a bit better.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] Just another portage enhancement idea...

[Rodolfo Boer]

Alle 16:36, martedì 11 ottobre 2005, José Carlos Cruz Costa ha scritto:
> Well, there's enotice.

However I think this has a broader scope, as many operations are replicated on 
different package merges, from notifying the user to regenerating system 
files (see docbook dtd's, info nodes, regenerating ld.so.cache, gnome-related 
stuff...), all things that could be delayed until the end when emerging 
multiple packages, so maybe an unified framework to delay arbitrary 
operations (with checks for duplicates) could save time when emerging as well 
as solving this issue.

My knowledge of portage internals is limited, so take this as a request for 
comments, any feedback is welcome, as long as it increases my knowledge :)

-- 
Move -- Proudly abusing Gentoo Base System version 1.12.0_pre9
        Linux 2.6.13-gentoo-r3

-- 
gentoo-dev@gentoo.org mailing list