On 02/09/2017 12:59 PM, Michael Orlitzky wrote: > On 02/09/2017 03:41 PM, Daniel Campbell wrote: >> That's a great question. Based on a cursory look at make.conf's manpage, >> USE_ORDER without 'pkginternal' will ignore IUSE defaults as intended. >> > > This has already been suggested like five times =P > > So long as people insist on using IUSE defaults for flags that are > critical to the package and to satisfy REQUIRED_USE (sprinkled liberally > throughout the tree), this won't work. You'll turn off the defaults that > are critical, too, and throw a wrench into dependency resolution. > >
(Just noticed that after I finished reading the thread; d'oh) Hm, good point. A good number of us are against REQUIRED_USE (I don't feel strongly either way), and I'm really not sure why we have packages that won't work at all without specific USE flags. Now that I've read the entire thread I see someone mentioned different arches may need different USE flags, but that seems like something that belongs in the profile, *if* it's a profile problem. I'd be happy if REQUIRED_USE conflicts were handled in one of two ways: 1. emerge throws it up in your face and suggests a change (defaulting to whichever IUSE has a +), which can then be handled with etc-update or 2. emerge prompts you to choose a flag from the ones listed in REQUIRED_USE, obeys it, then does #1 so you can etc-update after merging. The downside to this is it's yet another function to add to emerge. I'm not sure how else we can make use of REQUIRED_USE while simultaneously allowing people the choice to not care. Could an eclass do this reliably? -- Daniel Campbell - Gentoo Developer OpenPGP Key: 0x1EA055D6 @ hkp://keys.gnupg.net fpr: AE03 9064 AE00 053C 270C 1DE4 6F7A 9091 1EA0 55D6
signature.asc
Description: OpenPGP digital signature
