When I set USE="-*" in make.conf ufed still shows the default USE flags, but portage does not set them, so ufed is not reliable. This is with portage-2.0.48-r1 and ufed-0.32. Reproducible: Always Steps to Reproduce: 1. set USE="-*" in make.conf 2. run ufed 3. compare ufed output with emerge -pv
I am sorry but I am having diffuculty understanding the problem. Can you please give me a specific example of what package you are installing and which flags are set.
This is the output of "emerge info | grep USE": USE="x86 3dnow aavm acl acpi acpi4linux crypt cups curl dga dnd dvd encode ethereal evo fbcon fbdev gb gd gif gnomedb gphoto2 gstreamer gtk2 imap ipv6 java jpeg junit libgda mad maildir mbox mcal md5sum mmx mng mozinterfaceinfo moznocompose moznoirc moznomail mozp3p mozsvg mozxmlterm music ncurses openal opengl pda pdflib pic plotutils pnp quicktime samba sasl slp tiff truetype type1 usagi usb v4l wmf wxwindows Xaw3d xface xinerama xml xml2 xmms xv xvid zlib gnome png python" I also made a screenshot of the ufed screen (see attachment). As you can see there are several flags shown activated in ufed that are not set for portage (aalib, alsa, arts, berkdb, bonobo, cdr, directfb and more that are not on the screenshot). All flags shown by emerge info are set in make.conf (except for x86), my USE settings there is: USE="-* 3dnow aavm acl acpi acpi4linux crypt cups curl dga dnd dvd encode \ ethereal evo fbcon fbdev gb gd gif gnomedb gphoto2 gstreamer gtk2 \ imap ipv6 java jpeg junit libgda mad maildir mbox mcal md5sum mmx mng \ mozinterfaceinfo moznocompose moznoirc moznomail mozp3p mozsvg \ mozxmlterm music ncurses openal opengl pda pdflib pic plotutils pnp \ quicktime samba sasl slp tiff truetype type1 usagi usb v4l wmf \ wxwindows Xaw3d xface xinerama xml xml2 xmms xv xvid zlib gnome png python" The same behavior can be reproduced with a simple USE="-*" in make.conf, ufed still shows the default flags.
Created attachment 14642 [details] Screenshot of ufed output
Ufed and portage are both behaving exactly as they are supposed to. Looking at the ufed screen shot you can see the following notation (+++), if the first symbol after the flag is a + it means that flag was enabled in /etc/make.profile/make.defaults. In your example they are all blank because the "-*" notation cancels them. The second symbol represents use flags that are set because you have installed the package that provided those functions. For instance if you install aalib then portage will automatically enable the aalib use flag. The "-*" does not effect how ufed or portage interprets those flags, "-*" will not disable those flags, it will only disable the the make.defaults flags. The mapping between use flags and packages is controlled by the /etc/make.profile/use.defaults file. The third flag represents the contents of the USE variable. This is the only variable that you should be changing. If you dont want the aalib flag enabled then reset it in ufed and ufed will add the -aalib flag to your USE variable. The next time you run ufed you will notice a - sign in the third column for aalib. If you run: emerge -pv --emptytree world you will notice that the flags that are set ( ie +flag) are the ones that ufed shows with a + in the second column. There are a few execptions. the x86, bootstrap and build flags are use internally by portage and should not be played with.
The behavior is not as you described, because I have aalib, alsa, arts and the other packages installed (I added the -* thing only recently) but portage does not show them as activated. Example: "emerge -pv mplayer" gives [ebuild U ] media-video/mplayer-0.90-r2 [0.90_rc5] +dga -oss +xmms +jpeg -3dfx -sse -matrox -sdl -X -svga -ggi -oggvorbis +3dnow -aalib +gnome +xv +opengl +truetype +dvd -gtk +gif -esd +fbcon +encode -alsa -directfb -arts -dvb ufed shows alsa, arts, ggi, X, sdl, oggvorbis, aalib, esd, gtk and directfb as active, but mplayer would be compiled wihtout them. The packages for these flags in use.defaults are installed. Ok, after a little portage debugging it seems that it is rather a portage bug or change in behavior (autouse is not merged into usesplit), still present in portage-2.0.49_pre11.
I agree, it sounds like portage has a bug or the default behavior changed and nobody told me. I will check with the portage maintainer this weekend and either file a portage bug if thats what it is or change ufed if its a feature change.
I just checked with the maintainer of portage, its a bug in portage and not ufed, I will start fixing tonight.
Fixed with version 0.33
