On 03/17/2017 03:19 AM, Walter Dnes wrote: > On Fri, Mar 17, 2017 at 02:09:29AM +0100, Ralf wrote > >> So somehow PYTHON_TARGET and PYTHON_SINGLETARGET got screwed on my >> system. I know how I could fix this for gedit only, but then other >> packages begin complaining about the same issue as well. > No, it's not screwed up. gedit insists on python 3.x now in > PYTHON_SINGLE_TARGET, given your USE flags. Start from the beginning. > app-editors/gedit-3.22.0::gentoo USE="introspection python spell" > You have (via package.use, make.conf, or profile) invoked the "python" > and "introspection" USE flags for gedit. The bit... Yes, I know what is wrong. But it's not only wrong for gedit, other packages will fail as well, if I correct the settings for gedit. > >> The following REQUIRED_USE flag constraints are unsatisfied: >> python? ( exactly-one-of ( python_single_target_python3_4 >> python_single_target_python3_5 ) ) > ...says that you need "exactly-one-of" the following... > ( python_single_target_python3_4 python_single_target_python3_5 ) > > Since you're using PYTHON_TARGETS="python3_4 -python3_5", the "local" > option is to add the following line to package.use to apply to gedit only. Yep, i know, and then the next package complains. So why didn't this happen before? What changed? > > app-editors/gedit python_single_target_python3_4 > > You might consider the "global" option, which is to change make.conf > to read PYTHON_SINGLE_TARGET="python3_4" if that doesn't cause rebuilds > all over the place. I already tried that. Then other packages complain because they are not compatible to the settings gedit requires. > > In either case, when upgrading from python 3.4 to 3.5 in the future, > you'll have to change "3.4" to "3.5" in make.conf and/or package.use. Can't I just enable some default settings somewhere? I don't want to introduce dozens of local settings for packages, especially as everything used to work before.
Ralf
