Sergey Popov posted on Tue, 11 Aug 2015 15:58:49 +0300 as excerpted: > 11.08.2015 15:30, Michael Palimaka пишет: >> On 11/08/15 20:10, Sergey Popov wrote: >>> Err, i have read the whole thread and still does not get a point, why >>> i am wrong. >> >> You clearly have not. The reasoning behind Qt team's policy is >> described on the page and has been reiterated on this list. You are >> undermining what little confidence there is in the QA team by making >> decisions with no consultation about problems you do not understand. >> >>> It's old battle like we have beforce with "gtk" meaning "any versions >>> of GTK flag". This behaviour should be killed with fire. >>> >>> Let's me reiterate some of the cases: >>> >>> 1. Package can be build without Qt GUI at all, but either Qt4 or Qt5 >>> can be chosen, but not both. >>> >>> Fix this with REQUIRED_USE, do not enable any of Qt flags by default >> >> Problem: this requires manual intervention if the user has both qt4 and >> qt5 USE flags enabled. >> >> > User choice of using USE flags is NOT a problem
[As has been said elsewhere in the thread but you apparently haven't seen...] But if the profile enables both qt4 and qt5, as at least one profile, the new plasma (aka kde5) profile does, and really must? The desktop profile enables qt4. The plasma profile inherits qt4 from there and enables qt5, so both are enabled. And because kde5 is an incremental switchover that still includes many kde4-based apps, some of which likely have deps that need qt4 in the USE flags and users likely still want it enabled in any case, it's not as simple as disabling the qt4 USE flag in the plasma profile, either. Furthermore, as qt5 matures and more apps base on it, it's likely that qt5 will need enabled in the desktop profile as well, well before qt4 can be conveniently disabled. So there's some users now, the ones using the plasma profile, and will soon be very many users, anyone using a desktop-inheriting profile, that will have and arguably need, both qt4 and qt5 enabled. You're really saying that *all* of them should be forced to deal with dozens of package-specific package.use settings, to negate the effects of REQUIRED_USE when both qt4 and qt5 are enabled in their gentoo-shipped profile? This is why it's a problem. If it were just the people that specifically set both qt4 and qt5 in make.conf. it'd be a much smaller problem and could perhaps be simply ignored as a user-created problem. But when it's the default setting in all desktop profiles, as it's very likely to be within a year, it's no longer simply a user-created problem. [Personally, I both run with USE="-* ..." and started trying qt5 and kde5/ plasma back when they were both still in the overlay, so I've long since worked out the biggest such problems here. I didn't complain as it's simply part of both trying things that far ahead and specifying that I /want/ the choice and will deal with the consequences of such things by setting USE=-*. But it'd be very nice if our stable desktop users didn't have to go thru the same thing I did, once they get plasma5, just because they use a desktop profile.] -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman
