[gentoo-portage-dev] a suggestion about einfo messages

[gentoo-portage-dev] a suggestion about einfo messages

[YiDa Chiang]

When I emerge some package (like python),it may show that you need to do 
something else if you upgrade from an older version.But if I emerge a lot of 
package,such messages might override by other's emerge progress.So 
can "einfo" save to a file temporarily.And,after all emerge done, show all 
of einfo messages?


--
gentoo-portage-dev@gentoo.org mailing list

Re: [gentoo-portage-dev] a suggestion about einfo messages

[Michael Kohl]

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

On Wed, 21 Jul 2004 16:22:34 +0800
"YiDa Chiang" <ccpz@sparc20.hchs.hc.edu.tw> wrote:

> But if I emerge a lot of package,such messages might override by
> other's emerge progress.

They are stored in the emerge logs:

# PORT_LOGDIR is the location where portage will store all the logs it
# creates from each individual merge. They are stored as YYMMDD-$PF.log 
PORT_LOGDIR=/var/log/emerge/

> So can "einfo" save to a file temporarily.And,after all emerge done,
> show all of einfo messages?

This thread [1] has a lot of handy portage utilities, including
portlog-info [2], which can show you this messages in a nice way.

Regards,
Michael

[1] http://forums.gentoo.org/viewtopic.php?t=67849
[2] http://tdegreni.free.fr/gentoo/portlog-info

-- 
www.cargal.org 
GnuPG-key-ID: 0x90CA09E3
Jabber-ID: citizen428 [at] cargal [dot] org
Registered Linux User #278726

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

Re: [gentoo-portage-dev] a suggestion about einfo messages

[Joseph Booker]

I think what he was saying, is that einfo (and i guess ewarn also) would
be redirected to a file, what about the same file as the regular
PORT_LOGDIR, but with *.einfos.log files also? (or instead of?)

On Wed, July 21, 2004 4:04 am, Michael Kohl said:
> On Wed, 21 Jul 2004 16:22:34 +0800
> "YiDa Chiang" <ccpz@sparc20.hchs.hc.edu.tw> wrote:
>
>> But if I emerge a lot of package,such messages might override by
>> other's emerge progress.
>
> They are stored in the emerge logs:
>
> # PORT_LOGDIR is the location where portage will store all the logs it
> # creates from each individual merge. They are stored as YYMMDD-$PF.log
> PORT_LOGDIR=/var/log/emerge/
>
>> So can "einfo" save to a file temporarily.And,after all emerge done,
>> show all of einfo messages?
>
> This thread [1] has a lot of handy portage utilities, including
> portlog-info [2], which can show you this messages in a nice way.
>
> Regards,
> Michael
>
> [1] http://forums.gentoo.org/viewtopic.php?t=67849
> [2] http://tdegreni.free.fr/gentoo/portlog-info
>
> --
> www.cargal.org
> GnuPG-key-ID: 0x90CA09E3
> Jabber-ID: citizen428 [at] cargal [dot] org
> Registered Linux User #278726
>


-- 
Joseph Booker
joe @ irc.neoturbine.net
jj110888 @ irc.freenode.net


--
gentoo-portage-dev@gentoo.org mailing list

Re: [gentoo-portage-dev] a suggestion about einfo messages

[Michael Kohl]

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

On Wed, 21 Jul 2004 10:29:32 -0500 (CDT)
"Joseph Booker" <joe@neoturbine.net> wrote:

> I think what he was saying, is that einfo (and i guess ewarn also)
> would be redirected to a file, what about the same file as the regular
> PORT_LOGDIR, but with *.einfos.log files also? (or instead of?)

Look, that's sample output from portlog-info:
=== 2004-07-08 12:56 === iptables-1.2.11-r2 ===
 = /var/log/emerge/4528-iptables-1.2.11-r2.log =
...
 * This package now includes an initscript which loads and saves
 * rules stored in /var/lib/iptables/rules-save
 * This location can be changed in /etc/conf.d/iptables
 *
 * If you are using the iptables initsscript you should save your
 * rules using the new iptables version before rebooting.
 *
 * If you are uprading to a >=2.4.21 kernel you may need to rebuild
 * iptables.
 *
 * !!! ipforwarding is now not a part of the iptables initscripts.
 * Until a more permanent solution is implemented adding the following
 * to /etc/conf.d/local.start will enable ipforwarding at bootup:
 *   echo "1" > /proc/sys/net/ipv4/conf/all/forwarding


As you can see these *ARE* the einfo lines, so there's no need for other
files like iptables.einfo.log, because the information is already there.
Or maybe I'm just not getting what you're trying to tell me, which is
always a possibility with me... ;-)

Regards,
Michael

-- 
www.cargal.org 
GnuPG-key-ID: 0x90CA09E3
Jabber-ID: citizen428 [at] cargal [dot] org
Registered Linux User #278726

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

Re: [gentoo-portage-dev] a suggestion about einfo messages

[Thomas de Grenier de Latour]

On Wed, 21 Jul 2004 10:29:32 -0500 (CDT)
"Joseph Booker" <joe@neoturbine.net> wrote:

> I think what he was saying, is that einfo (and i guess ewarn
> also) would be redirected to a file, what about the same file as
> the regular PORT_LOGDIR, but with *.einfos.log files also? (or
> instead of?)

That was one of the features of my "really quiet mode for emerge"
patchset, that you can still find here :
http://bugs.gentoo.org/show_bug.cgi?id=37491

I've stopped updating this patch after portage-2.0.50-r1, by
lack of time and feedback. But if you look at the ebuild.sh part
of the patch, you will find some piece of code that can help
implementing this idea.


-- 
TGL.

--
gentoo-portage-dev@gentoo.org mailing list

Re: [gentoo-portage-dev] a suggestion about einfo messages

[Joseph Booker]

On Wed, July 21, 2004 11:01 am, Thomas de Grenier de Latour said:
> On Wed, 21 Jul 2004 10:29:32 -0500 (CDT)
> "Joseph Booker" <joe@neoturbine.net> wrote:
>
>> I think what he was saying, is that einfo (and i guess ewarn
>> also) would be redirected to a file, what about the same file as
>> the regular PORT_LOGDIR, but with *.einfos.log files also? (or
>> instead of?)
>
> That was one of the features of my "really quiet mode for emerge"
> patchset, that you can still find here :
> http://bugs.gentoo.org/show_bug.cgi?id=37491
>
> I've stopped updating this patch after portage-2.0.50-r1, by
> lack of time and feedback. But if you look at the ebuild.sh part
> of the patch, you will find some piece of code that can help
> implementing this idea.

<quote>
 - Optionnaly, by defining PORT_SHORTLOGDIR, user can choose to keep a quiet
   version of the logs, similar to the quiet display.
</quote>

yea, that part is what i figured he meant.

-- 
Joseph Booker
joe @ irc.neoturbine.net
jj110888 @ irc.freenode.net


--
gentoo-portage-dev@gentoo.org mailing list

Re: [gentoo-portage-dev] a suggestion about einfo messages

[Thomas de Grenier de Latour]

On Wed, 21 Jul 2004 17:51:59 +0200
Michael Kohl <citizen428@cargal.org> wrote:

> As you can see these *ARE* the einfo lines, so there's no need
> for other files like iptables.einfo.log, because the information
> is already there. 

Well, portlog-info was really a quick and dirty hack (i can tell
that since i wrote it). Greping for some escape sequence in a
log file is just insane :)
Sure, that's still better than nothing, but a solution at
ebuild.sh level would be much better.  

-- 
TGL.

--
gentoo-portage-dev@gentoo.org mailing list

Re: [gentoo-portage-dev] a suggestion about einfo messages

[Michael Kohl]

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

On Wed, 21 Jul 2004 18:15:19 +0200
Thomas de Grenier de Latour <degrenier@easyconnect.fr> wrote:

> Sure, that's still better than nothing, but a solution at
> ebuild.sh level would be much better.  

True, I never wanted to argue about that. 

I just thought the OP might be interested in a solution for his
problems that works right away, and portlog-info does that just fine,
hack or not. :)

Regards,
Michael

-- 
www.cargal.org 
GnuPG-key-ID: 0x90CA09E3
Jabber-ID: citizen428 [at] cargal [dot] org
Registered Linux User #278726

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

[gentoo-portage-dev] Re: a suggestion about einfo messages

[Joel Konkle-Parker]

Michael Kohl wrote:
> They are stored in the emerge logs:
> 
> # PORT_LOGDIR is the location where portage will store all the logs it
> # creates from each individual merge. They are stored as YYMMDD-$PF.log 
> PORT_LOGDIR=/var/log/emerge/

What logs are these? I have a default setup, and the only log I see is 
/var/log/emerge.log, which doesn't contain any einfo or ewarn messages 
whatsoever.


-- 
Joel Konkle-Parker
Webmaster  [Ballsome.com]

E-mail     [jjk3@msstate.edu]


--
gentoo-portage-dev@gentoo.org mailing list

Re: [gentoo-portage-dev] Re: a suggestion about einfo messages

[Joseph Booker]

On Wed, July 21, 2004 4:30 pm, Joel Konkle-Parker said:
> Michael Kohl wrote:
>> They are stored in the emerge logs:
>>
>> # PORT_LOGDIR is the location where portage will store all the logs it
>> # creates from each individual merge. They are stored as YYMMDD-$PF.log
>> PORT_LOGDIR=/var/log/emerge/
>
> What logs are these? I have a default setup, and the only log I see is
> /var/log/emerge.log, which doesn't contain any einfo or ewarn messages
> whatsoever.
>

uncomment PORT_LOGDIR in your make.conf

then emerge something

then youll get a /var/log/portage/*-packages*.log containing what they are
talking about


-- 
Joseph Booker
joe @ irc.neoturbine.net
jj110888 @ irc.freenode.net


--
gentoo-portage-dev@gentoo.org mailing list

[gentoo-portage-dev] Re: a suggestion about einfo messages

[Joel Konkle-Parker]

Joseph Booker wrote:
> uncomment PORT_LOGDIR in your make.conf

For what it's worth, I don't have that in my make.conf or in my 
make.globals.

I installed with 2004.1. This little logging tidbit isn't in the 
Handbook either.

Surely this should be a default and very publicized feature. I happen to 
agree with the OP that emerge should cache the messages and display them 
at the end.


-- 
Joel Konkle-Parker
Webmaster  [Ballsome.com]

E-mail     [jjk3@msstate.edu]


--
gentoo-portage-dev@gentoo.org mailing list

Re: [gentoo-portage-dev] Re: a suggestion about einfo messages

[Kumba]

Joel Konkle-Parker wrote:

> For what it's worth, I don't have that in my make.conf or in my 
> make.globals.
> 
> I installed with 2004.1. This little logging tidbit isn't in the 
> Handbook either.
> 
> Surely this should be a default and very publicized feature. I happen to 
> agree with the OP that emerge should cache the messages and display them 
> at the end.

Unpack a portage tarball, and the x86 make.conf file will be in the cnf/ 
folder.

A small (IMHO) bug in catalsyt (the utility that builds stages) 
generates its own make.conf file, and I think after building, it should 
copy over a full portage make.conf for users, as the catalyst generated 
one lacks comments and such.


--Kumba

-- 
"Such is oft the course of deeds that move the wheels of the world: 
small hands do them because they must, while the eyes of the great are 
elsewhere."  --Elrond

--
gentoo-portage-dev@gentoo.org mailing list

[gentoo-portage-dev] Re: a suggestion about einfo messages

[Joel Konkle-Parker]

Kumba wrote:
> A small (IMHO) bug in catalsyt (the utility that builds stages) 
> generates its own make.conf file, and I think after building, it should 
> copy over a full portage make.conf for users, as the catalyst generated 
> one lacks comments and such.

Hopefully this will be fixed in 2004.2? In 2004.1, the user starts out 
with a completely blank make.conf, and a new one never gets copied over.


-- 
Joel Konkle-Parker
Webmaster  [Ballsome.com]

E-mail     [jjk3@msstate.edu]


--
gentoo-portage-dev@gentoo.org mailing list

[gentoo-portage-dev] SSE2 and MMX2 use flags.

[Roman Gaufman]

Hey,

From my experience, on older and compact laptops, to install gentoo, many 
compile gentoo on their PC, and then copy over installation to laptop hard 
drive (using a 2.5" to 3.5" converter or over network).  There is a problem 
however.

Even if selecting to compile for the laptop in question, things like sse2 and 
mmx2 are auto detected, atleast in mplayer. That makes mplayer crash on 
startup when copied to laptop. 

What I recommend is to add an sse2/mmx2 use flags and if no use flag for 
mmx/sse/mmx2/sse2 is set, then auto detect, otherwise either force it, or 
force against it.

Your thoughts?

Hackeron

--
gentoo-portage-dev@gentoo.org mailing list

Re: [gentoo-portage-dev] SSE2 and MMX2 use flags.

[Marius Mauch]

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

On 07/25/04  Roman Gaufman wrote:

> Hey,
> 
> From my experience, on older and compact laptops, to install gentoo,
> many compile gentoo on their PC, and then copy over installation to
> laptop hard drive (using a 2.5" to 3.5" converter or over network). 
> There is a problem however.
> 
> Even if selecting to compile for the laptop in question, things like
> sse2 and mmx2 are auto detected, atleast in mplayer. That makes
> mplayer crash on startup when copied to laptop. 
> 
> What I recommend is to add an sse2/mmx2 use flags and if no use flag
> for mmx/sse/mmx2/sse2 is set, then auto detect, otherwise either force
> it, or force against it.
> 
> Your thoughts?

That's a ebuild problem for mplayer, not a portage problem.

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-portage-dev] SSE2 and MMX2 use flags.

[Roman Gaufman]

Not particularly mplayer, as the only reason they won't fix it is because of a 
lack of see2 and mmx2 use flags in portage. But yes, I should've emailed 
gentoo-dev, not gentoo-portage-dev.

On Sunday 25 July 2004 16:16, Marius Mauch wrote:
> On 07/25/04  Roman Gaufman wrote:
> > Hey,
> >
> > From my experience, on older and compact laptops, to install gentoo,
> > many compile gentoo on their PC, and then copy over installation to
> > laptop hard drive (using a 2.5" to 3.5" converter or over network).
> > There is a problem however.
> >
> > Even if selecting to compile for the laptop in question, things like
> > sse2 and mmx2 are auto detected, atleast in mplayer. That makes
> > mplayer crash on startup when copied to laptop.
> >
> > What I recommend is to add an sse2/mmx2 use flags and if no use flag
> > for mmx/sse/mmx2/sse2 is set, then auto detect, otherwise either force
> > it, or force against it.
> >
> > Your thoughts?
>
> That's a ebuild problem for mplayer, not a portage problem.
>
> Marius

--
gentoo-portage-dev@gentoo.org mailing list