Re: [gentoo-portage-dev] Additional information to output: emerge -pv

[Dustin Spicuzza]

> The appropriate way would be to open a bug in bugzilla, assign it to 
the portage team
 > and attach the patch there (normally each file separately, not packed 
in a tarball)

Thanks. Will do.

 > How about making it so you need two -v switchs (eg: -vv) to get the 
long listing? I use
 > `emerge world -puv` all the time and don 't want to have to scroll 
through so much stuff.

Good idea... it shouldn't be a big deal to do that... I was just trying 
to keep the patch nice and simple.

 > Does it repeat the same use flags over and over again for each 
package, or just explain
 > it once? Also, does it distinguish local from global use flags?

It repeats the USE flags for each package, but ONLY the use flags that 
apply to that package. Personally, I think this is a more desirable 
behavior, because of when you do something like 'emerge world', then 
you'll have this really BIG list of stuff, and lots of repeating USE 
flags. However, it puts a empty line between each package, so that each 
list of USE flags is shown nicely for each package.. like this:

[stuff here] package useflag useflag2
* useflag - does something
* useflag2 - does something else

[stuff here] package useflag3 useflag
* useflag3 - does yet another thing
* useflag - does something

And so on... for the entire list. Currently, it searches global flags 
first, then falls back to local flags... but you're right -- its a 
better idea to search locals first, then globals. I don't really think 
its necessary though to note that its a local flag or a global flag... 
its not like it matters too much when you're trying to decide whether 
you want to set it or not. You just want to know what the package wants 
to use it for. I spose it could do something like * [local] useflag - 
description, and * [global] useflag - description...

Dustin
-- 
gentoo-portage-dev@g.o mailing list