Talk:Gentoo setup
From LinodeWiki
[edit] USE Flag Suggestions/Recommendations
I am using the following USE in /etc/make.conf:
USE="-X -gtk -gnome -alsa -qt -apm -arts -avi -cups -emboss -encode -foomaticdb -gpm -gtk2 -kde -libg++ -mad -mikmod -motif -mp3 -mpeg -oggvorbis -opengl -oss -quicktime -sdl -svga -truetype -truetype-fonts -xmms -xv"
I prefer adding flags as needed when installing pkgs.
A slightly different version of the USE flags (diffs in bold):
USE="-X -gtk -gnome -alsa -qt -apm -arts -avi -cups -emboss -encode -foomaticdb -fortran -gpm -gtk2 -kde -libg++ -mad -mikmod -motif -mp3 -mpeg -oggvorbis -opengl -oss -quicktime -sdl -svga -truetype -truetype-fonts -xmms -xv -perl"
--Markph 21:03, 26 Sep 2005 (EDT)
I added some basic recommended USE flags to the main Gentoo page before I realized there was some work being done on what USE flags to list here. Joining into the discussion...
I can't honestly say there's a single USE flag mentioned in either of your configs that I would leave out of my own configuration, however, I could see people needing, for example, truetype fonts along with whatever image lib they're using (GD, ImageMagick, NetPBM, etc) to render specific fonts on images. I would keep the recommended Linode Gentoo USE flags down to a minimum. Besides that, once you've got the flags to avoid emerging X, Gnome, and KDE, there's not a lot that's really going to make much of an impact. My viewpoint also comes from some experience setting up Gentoo 3 years ago when I thought I could just go through the USE flags one by one, and toss in all the ones that looked good, and take out the ones I knew I wasn't going to use. Needless to say, I had to re-install from scratch a week later after running into way too many problems. It's been mentioned in the Gentoo docs in the past not to go crazy with the USE flags in make.conf. Along those notes, even on my desktop and laptop at home, I use the /etc/portage/package.use file and specify per package USE flags for all minor flags (which I only usually need for one specific package anyway).
If anyone can fill in details on what caker has setup in the 2005.1 image, that would come in helpful. Depending on what's installed, what USE flags have been set up to that point, what stage the image was installed with, and what USE flags were changed if any and when, it can make an impact on what flags are safe to use globablly in make.conf, and whether subsequent flags may be better off as package specific USE flags (in /etc/portage/package.use) if they have to be used. I typically recommend to Gentoo users to use package specific USE flag settings anyway when it's applicable. It's there to cut back on problems.
As of right now, I'd personally just suggest the following flags as recommended:
USE="-X -gtk -gtk2 -gnome -qt -kde -alsa"
Other flags that work different based on the environment (being in UML on Linode) should definately be mentioned if any are known.
--tierra 21:39, 26 Sep 2005 (MST)
I'd rather have to recompile stuff later on when I know it's needed, rather than have it taking up space. I'm on the lowest plan so space is a consideration for me. To be honest, it's always a consideration. My first home computer used a cassette tape for storage and it's colored how I do everything. :]
[edit] [ --depclean ] Option
Someone has asked me why I don't have emerge --depclean in my update script. I've read some forums (don't have them handy at the moment) that suggests this might be a bad idea. Anyone know one way or the other? Does revdep-rebuild take care of this?
emerge --depclean has the tendancy to delete libraries still in use by some applications (ones that miss specifying the dependancy it's cleaning out since most systems have it installed already from other packages meaning the package doesn't get rebuilt on the new version when it's updated and cleaned). revdep-rebuild does fix most problems people have with this but it's been known to be un-intuitive how it works and how to use it and many people run into more work than they were expecting when they use --depclean for those that don't understand the build process, libraries, and what --depclean does. Most of the time it's not even necessary, doesn't clean out all that much diskspace, and isn't worth the effort for some of the problems it causes. It should only be used in cases where it's necessary to get some functionality working, and those issues are typically worked out by the package admins before it goes stable making sure it has the correct version dependancies for it's newer functionality.
--tierra 18:10, 12 Oct 2005 (MST)
