/etc/make.conf is a modification to the USE env var in /etc/make.profile/make.defaults, not a replacement for it. To obtain the proper set of active USE flags that emerge/ebuild use, you will have to apply a masking algorithm. The "net" USE flag result should be calculated, thus: 1) source /etc/make.profile/make.defaults and pick out the contents of the USE var into a tmp env var, say default_use 2) source /etc/make.conf and pick out the contents of the USE var into a different tmp env var, say conf_use 3) A USE var foo is in the "net" USE flag set either of the follow cases is correct: a) It appears in default_use and -foo is not in conf_use b) It appears in conf_use (without a - sign in front, obviously)
I'll begin work adding the net USE value calculation to any areas where the USE variable is displayed. Would you like me to break "show" into two features, one that displays what the user has placed into /etc/make.conf, and one displaying the net value of USE? I'm just now getting my primary workstation back online after a hard drive failure (HD was < 4 months old), so I didn't know about this until a couple of days ago. Please give me a few days while I get everything together. Thanks.
You may add a --no-calc option or somesuch that allows the user to see what's in /etc/make.conf, but I consider that unecessary, as what one really wants to know is the end-result.
Gaarde <gaarde@yahoo.com> is working on a new version of useflag, so I'm closing this one. If you're interested in joining the useflag party, please contact Gaarde.
