On Tuesday 16 September 2003 09:08, Stroller wrote: > >>> bash-2.05b#less make.defaults > >>> > >>> USE="x86 oss apm arts avi berkdb crypt cups encode foomaticdb gdbm > >>> gif > >>> gpm gtk imlib java jpeg kde gnome libg++ libwww mad mikmod mmx motif > >>> mpeg > >>> ncurses nls oggvorbis opengl pam pdflib png python qt quicktime > >>> readline > >>> sdl slang spell ssl svga tcpd truetype X xml2 xmms xv zlib" > >>> > >>> ARCH="x86" > >>> COMPILER="gcc3" > >>> ACCEPT_KEYWORDS="x86" > >> > >> Better to simply look at the output of 'emerge info' > > > > Again, I think it's better to look at make.defaults. At least then you > > know > > where the use flags are coming from. > > I think it's better to look at `emerge info`: it is in /etc/make.conf > that any changes should be made, users are discouraged from changing > make.defaults. Encouraging users to look in make.defaults to see where > "their" defaults come from fosters the risk of them editing it.
I get your point. I should have been clearer. What I meant was just to take a glance at it to know how the system works. It clears up the question of why -flag is needed in make.conf. > Joshua: you might find `emerge ufed` useful for helping you edit your > USE flags. ufed is a very good idea. It not only shows composite and breakdown of all use flag settings and locations. > I always run `emerge -upv somefile` before emerging it for real - the > -v flag tells you which USE flags it wants to use. Also a good idea.... Jason -- [EMAIL PROTECTED] mailing list
