Floyd Anderson wrote: > On Sun, 05 Feb 01:44:30 -0600 > Dale <rdalek1...@gmail.com> wrote: >> the...@sys-concept.com wrote: >>> >>> I change in make.conf to: >>> USE="bindist" >>> >>> and I was able to install basic system correctly, network is working >>> and I can proceed with castomazation but >>> my next question: What is the correct way to configure "USE=" in >>> make.conf? >>> >>> When I use a below: (copied from my other systems): >>> >>> USE="-qt4 -kde -gnome -arts -berkdb -acl X gtk alsa cups apache2 ssl >>> foomaticdb truetype kpathsea ppds mysql udev tiff png usb scanner >>> gimp gimpprint cgi fam nptl type1 opengl tetexspell consolkit dbus >>> pam policykit jpeg lock session startup-notification thunar >>> cleartype corefonts -systemd -DOPENSSL_NO_HEARTBEATS abi_x86_32" >>> >>> PS. I think "dbus" is no longer used, isn't it? >>> <<< SNIP >>> >>> -- >>> Thelma >>> >>> >> >> >> Ask anyone, I'm different on the way I do USE flags, or I feel that >> way. If I have a flag that I want enabled/disabled on basically >> everything that uses that flag, it goes in make.conf. If I have a USE >> flag that I may need for just a few packages, or a single package, I put >> it in package.use. As a example. The kde USE flag. Since I run mostly >> KDE and want any packages I build to work with KDE, it goes in >> make.conf. To go with the other direction on this. qt4 and qt5. Some >> packages work or look better with one or the other. For those >> exceptions, I use package.use to set those. Since emerge reads >> package.use last, those setting apply. >> >> Basically, make.conf is the rule for USE flags. Package.use is for >> exceptions to that rule. >> >> As usual, do what makes the most sense to you. I post this just in case >> this way may make sense, not that much of anything I do makes sense to >> anyone else. ;-) >> >> Dale >> >> :-) :-) >> > > Recently I read an interesting post [1] (especially the middle > paragraph about the USE-flag ‘threads’ example). It let me rethink how > I handle USE (which is even similar your way) and it might be worth to > consider why a package maintainer defaults a flag on/off. > [1] > <https://archives.gentoo.org/gentoo-dev/message/a59f08ffe21bcf984ee82fd7125e0bf2> > >
I'm subscribed there and recall reading that. The point of my post was not for a specific flag. I just picked a flag that has been around for a long time and pretty much everyone recognizes what it is for. As I mentioned in another post, I could have picked many other flags. X, gnome, cups, or any number of others. The biggest point, there are many ways to handle USE flags. Pick what works for you and more importantly, makes sense to you. Anytime us Gentoo users are installing/upgrading/adding packages, we have to watch for changes or even new flags that may not be set the way we want. It's up to us on how to manage it. I posted my way, others can post their way. The OP can pick whichever makes the most sense to them. I might add, there are flags that we can't change. Those are set by upstream or the devs. My post wasn't about that either. It was all about managing options that we can change.. Rich has some good points at times. I try to read his posts unless it is something that doesn't interest me. I think he also supports the point I was making in my post. You have choices on how to do things, pick the one that works and does what you need. It's a strong point for Gentoo. I think USE flags are one of the biggest features of Gentoo. It's not like we have a fancy installer that can read our minds. ROFL It is interesting to see and read how others do this tho. It's amazing sometimes how many different ways the same thing can be managed and still work. I'm not sure any other distro can do that, not that I used others in a long time. Dale :-) :-)
