Results 51 to 60 of 67
Enjoy an ad free experience by logging in. Not a member yet? Register.
USE="mp490 symlink extras 3dnow acc acpi acl alsa arts asf avi avahi bitmap-fonts cddb cdparanoia cdr crypt cups dbus dvd eds encode ffmpeg firefox flac fortranf77 foomaticdb ftp gdbm gphoto2 gif glitz gnutls gpm gstreamer gtk hal imlib java jpeg kerberos kde ldap libg++ libwww lmsensors mad mailwrapper mbox mcal mdnsresponder-compat mikmod mime mmx motif mp3 mpeg mplayer mysql ncurses nls nvidia oggvorbis opengl pam parport pdflib png ppds python oav qt4 quicktime readline ruby samba sdl snmp spell ssl startup-notification svga tcpd truetype type1 usb win32codecs yahoo X xcomposite xine xml xml2 xmms xcb xvid xv xvmc zeroconf zlib"
Hope you don't mind slight friendly critics?
mp490 - who is that?
symlink - minor flag, I prefer doing it manually when ready for upgrade
arts - it's dead
avahi, mdnsresponder-compat, zeroconf - lazy we are ...
gpm - never had any use for this one
gtk - not needed for KDE system
hal - isn't it time to drop this one?
nls - why should you need this?
parport - really? exotic hardware?
oav - what's this?
tcpd - is it a server?
win32codecs - oh dear, haven't used this one for years, what it is ffmpeg cannot do for you?
I prefer automagically linking to the new kernel
old flag left over from previous install
not lazy, this is how I run my system. I don't think lazy people use Gentoo.
Console based mouse
I had Gnome, it's gone now, will be removed
Not sure, I can't remember now.
It was added when I couldn't get printer to work
it just works
Actually, setting all USE flags in make.conf is kind of obsolete. There are desktop subprofiles for KDE and Gnome users which set good defaults. One can do some fine tuning in make.conf by adding or disabling flags. In many cases systemwide setting is not the best and flags should be set in package.use instead.
Plus, all combinations of USE flags should work. If not then it warrants a bug report. In this case we need emerge --info output instead.
I'd say this thread is obsolete, too, and has no practical value. I'd recommend un-sticking it or moving into Coffee Lounge.
BTW, win32codecs are nowadays just a bunch of blobs, not needed for majority of users. I dropped this flag three or four years ago in all my boxes and never missed it.
I'll confer with a few other Gentoo'ers to find their viewpoints...if they agree with you then I'll unsticky this.
So what did you use to replace win32codecs? I use it for Mplayer. Does ffmpeg do the same things?
There are system-wide USE flags you want. Most of them come with your chosen profile (unless you go with lean /10.0 as I do, in this case you have to complete your own set).
There are local USE flags, per package. It may be reasonable to set these in package.use so they won't clutter your make.conf.
There are some USE flags you may want to enable for certain packages only, in order to keep the system as lean as possible. These go to package.use, too.
I did no special effort to replace win32codecs, I just realized ffmpeg does all I ever need.
I'd say remove this USE flag and do something likeCode:
emerge -avuNDt --with-bdeps=y @worldCode:
emerge -avuNDt --with-bdeps=y system world
Then use your box, I'm pretty sure you won't miss anything.
Handbook is a great help for beginners, good reference for regular users. Lots of aspects are not handled there, Handbook also falls often behind development.
For instance, prelinking is nowhere in Handbook. Although it is essential when building a desktop system.
USE flags in make.conf
To illustrate what I said before. First block is a snippet from emerge --info output.
USE="X acpi alsa amd64 berkdb bzip2 cairo cli cups cxx dbus dga dri exif fftw flac fontconfig fortran gdbm gnutls iconv id3tag imagemagick jbig jpeg lcms libsamplerate mmx modules mp3 mp4 mudflap multilib ncurses nptl nptlonly nsplugin ogg opengl openmp pam pcre pdf perl png policykit python readline sdl session spell sse sse2 sse3 ssl ssse3 svg sysfs threads thunar unicode usb vdpau vorbis xcomposite xft xinerama xorg xv xvmc zlib"
USE="X acpi alsa cairo dbus dga exif fftw flac fontconfig gnutls id3tag imagemagick jbig jpeg lcms libsamplerate mp3 mp4 nsplugin ogg opengl pdf png policykit sdl spell sse3 ssse3 svg threads thunar usb vdpau vorbis xcomposite xft xinerama xv xvmc -32bit -abiword -accessibility -acl -cracklib -crypt -doc -gpm -hal -imap -ipv6 -isdnlog -networkmanager -nls -pppd -reflection -startup-notification -tcpd -udev"
Just to add some color to above ... a snippet from emerge --info sys-devel/gcc
output - do you see graphite USE flag in above blocks? Yet, gcc is built with graphite ...
sys-devel/gcc-4.4.4-r2 was built with the following: USE="fortran graphite mudflap (multilib) nptl openmp (-altivec) -bootstrap -build -doc (-fixed-point) -gcj -gtk (-hardened) (-libffi) -multislot (-n32) (-n64) -nls -nocxx -nopie -nossp -objc -objc++ -objc-gc -test -vanilla" CFLAGS="-march=core2 -O2 -pipe" CXXFLAGS="-march=core2 -O2 -pipe"
Very cool. Where did you learn this? You got a link? It ain't in the handbook just like prelinking. Are you checking the USE flags in make.defaults and adding or removing what you want from that?
BTW I use Portage 2.1.
I've got no link, just six years of Gentoo under my belt.
I do check USE flags when I install or upgrade. Using -va option with emerge you can have a look at active/inactive flags before you build. If you see something you do not like you override it in make.conf or package.use.
I say override, because defaults are set for arch, profile and often also for package (in ebuild).
BTW, sometimes it is more than USE flags you want to set:
[ebuild R ] media-gfx/sane-backends-1.0.21-r1 USE="usb -avahi -doc -gphoto2 -ipv6 -v4l" SANE_BACKENDS="net -abaton -agfafocus -apple -artec -artec_eplus48u -as6e -avision -bh -canon -canon630u -canon_dr -canon_pp -cardscan -coolscan -coolscan2 -coolscan3 -dc210 -dc240 -dc25 -dell1600n_net -dmc -epjitsu -epson -epson2 -fujitsu -genesys -gt68xx -hp -hp3500 -hp3900 -hp4200 -hp5400 -hp5590 -hpljm1005 -hpsj5s -hs2p -ibm -kodak -kvs1025 -leo -lexmark -ma1509 -matsushita -microtek -microtek2 -mustek -mustek_pp -mustek_usb -nec -niash -p5 -pie -pixma -plustek -plustek_pp -qcam -ricoh -rts8891 -s9036 -sceptre -sharp -sm3600 -sm3840 -snapscan -sp15c -st400 -stv680 -tamarack -teco1 -teco2 -teco3 -test -u12 -umax -umax1220u -umax_pp -xerox_mfp"
To sum it up, I really do not care what USE flags are set system-wide or at package level as defaults. I do care what flags (and other options) are in effect when I build a given package.
Even after fresh install when it is time for emerge -e system I do it with -v option, so I can have a look and possibly correct something before essential system rebuild.
As you see, USE flags in make.conf are merely for overriding defaults, this is why I suggest unsticking this thread.
P. S. There are nice tools like ufed in portage that help you organize your flags, ufed does not read package.use, though.
I must admit my last install looks to date from January 2009 - so things may have moved on in terms of the install process ...