Walter Dnes wrote: > On Sat, Mar 14, 2020 at 03:17:34PM +0100, hitachi303 wrote >> Am 14.03.20 um 13:46 schrieb Neil Bothwick: >>> I take it you don't have USE=libglvnd for mesa? >> Yes I do. Since I haven't defined it in my make.conf I guess it is >> defined by profile. > When I update my system, I do a pretend emerge and check for new > packages and flags. I saw this flag, and asked for "Mr. Google's > opinion". There were a few horror stories, so I added "-libglvnd" to my > USE flags in make.conf, and things run fine after the update. I'll > check back later down the road, when the kinks are hopefully worked out. >
I do similar myself. I use the -a option that way IF, big IF, everything looks OK I can hit y and enter to carry on without it going through the process again. I to look for changed USE flags. I use euse -i to see what they are for, which usually doesn't help much. I then use eix to find the package it pulls in if it is a lib<something> and hit up the home page to see what it does. Sometimes I let it apply then test the software to see if I want to keep it or not. Sometimes I disable it in package.use for that package(s). Like you, depends on what it does. Sometimes I don't need that feature, sometimes I just don't want it, sometimes it may not work here due to hardware limits. I don't have a mic input for example or a video camera either. Sort of hard for software to configure something it can't find because it doesn't exist. Other examples could apply as well. When doing upgrades, I agree it is always wise to look at all USE flag changes. Having USE flags is a Gentoo feature but if not monitored correctly, it can be a curse as well. It can cause havoc and makes things not work correctly or add features one doesn't want. +1 to this. Dale :-) :-)
