* Jason Rhinelander <[EMAIL PROTECTED]> [2003-12-08 18:31:16 -0800]: > Joel Konkle-Parker wrote: > > # emerge -pv packagename otherpackage
> Calculating dependencies ...done! > [ebuild N ] abc-xyz/packagename-1.2.3-r4 +aaa -bbb -ccc > [ebuild N ] abc-xyz/otherpackage-4.3.2-r1 +gnome -curses +cgi > # emerge -pvv packagename otherpackage > Calculating dependencies ...done! > [ebuild N ] abc-xyz/packagename-1.2.3-r4 +aaa -bbb -ccc > aaa - gives you aaa client support > bbb - gives you bbb server support > ccc - makes packagename do strange and unusual things with ccc" > [ebuild N ] abc-xyz/otherpackage-4.3.2-r1 +gnome -curses +cgi > gnome - adds gnome control center support > curses - adds curses management support > cgi - gives you management support via an installed CGI script Looks really nice. I'm not sure if it changes the situation very much, but I'm not too worried to start with. It _does_ encourage the user to modify the flags per package which is something I'd only do in special cases. What's really important to me in these cases is that when I `emerge -u otherpackage', or `emerge -u world' and thereby upgrading otherpackage, portage must _remember_ the USE flags I originally used to emerge otherpackage. Otherwise I may suddenly find myself without CGI support one day and the system will be broken. Eivind -- [EMAIL PROTECTED] mailing list
