With qt 4.8.6 and qt5 headed for the tree at some point, along with their dependence on qtchooser, I'm guessing some package (qtcore?) in each will eventually setup a somewhat standard qtchooser profile, and that most likely, the qt eclasses will automatically set QT_SELECT to select the appropriate profile based on dependencies for packages inheriting the appropriate eclass. I'm beginning to experiment with at least qt 4.8.6 from the overlay (and tried qt5/plasma5 for a bit, but decided it was too early for that yet so unmerged right away), but of course those assumed profiles aren't setup yet so I'm having to manually setup my own. What format are these gentoo/qt standard qtchooser profile names going to take, and should I try to match them or avoid them with the ones I setup myself? Right now, I've simply setup a "4" profile (selected with QT_SELECT=4, with that set as the default for the moment at least), and when I was earlier experimenting with plasma5 (which I unmerged after playing a bit as "too early still"), of course I setup a "5" profile as well. But I expect the gentoo/qt standard profiles will be a bit more verbose than that, say qt4 and qt5, at minimum, or possibly qt4.8 or qt-4.8.6 (and similar for qt5). If I knew what the standard names were going to be I could either set mine up to match, or alternatively, set mine up so they don't conflict if that's preferred/recommended. I realize this is more a question than a bug, except to the extent that lack of mention /anywhere/ I can find (and I looked, if it's there I think I'm blind, ALL bugz returned zero for a qtchooser search, too!), perhaps in some qt-overlay Documentation/README file or the like, might be considered a bug, but I'm sure others will be asking it too if they aren't already, and hopefully with an appropriately keyword searchable bug summary at least some of them can find this bug/question before they ask it themselves. Plus maybe it'll prompt such a readme. =:^) Thanks. Having a bit of experience now with the qt5/plasma5 stuff in its current state, I have at least /some/ appreciation of the problems you guys are working thru!
(In reply to Duncan from comment #0) > With qt 4.8.6 and qt5 headed for the tree at some point, along with their > dependence on qtchooser, I'm guessing some package (qtcore?) in each will > eventually setup a somewhat standard qtchooser profile, and that most Correct, qtcore:4 will create the "system" qtchooser profile for qt4, likewise for qtcore:5 and qt5. > likely, the qt eclasses will automatically set QT_SELECT to select the > appropriate profile based on dependencies for packages inheriting the > appropriate eclass. I guess we could set the env variable as a backward-compat measure, but eqmake{4,5} will use the full path to the real qmake executable in /usr/$libdir/qt{4,5}/bin/ Other build systems (cmake especially) will probably need adjustments. > > I'm beginning to experiment with at least qt 4.8.6 from the overlay (and > tried qt5/plasma5 for a bit, but decided it was too early for that yet so > unmerged right away), but of course those assumed profiles aren't setup yet > so I'm having to manually setup my own. > qt-4.8.6 from the overlay is a work in progress and known to be broken in a few ways in its current state. > What format are these gentoo/qt standard qtchooser profile names going to > take, and should I try to match them or avoid them with the ones I setup > myself? > > Right now, I've simply setup a "4" profile (selected with QT_SELECT=4, with > that set as the default for the moment at least), and when I was earlier > experimenting with plasma5 (which I unmerged after playing a bit as "too > early still"), of course I setup a "5" profile as well. But I expect the > gentoo/qt standard profiles will be a bit more verbose than that, say qt4 > and qt5, at minimum, or possibly qt4.8 or qt-4.8.6 (and similar for qt5). > Well using anything more than $SLOT is pointless. So I was thinking about "qt4" and "qt5", possibly with something to distinguish between multilib ABIs (not sure about this though). > If I knew what the standard names were going to be I could either set mine > up to match, or alternatively, set mine up so they don't conflict if that's > preferred/recommended. > Good point. In addition to the system folder, people can set up their own profiles in ~/.config/qtchooser IIRC, therefore some "namespacing" would be good I guess. Maybe "gentoo-qt4" or "system-qt4"? Suggestions welcome. > I realize this is more a question than a bug, except to the extent that lack > of mention /anywhere/ I can find (and I looked, if it's there I think I'm > blind, ALL bugz returned zero for a qtchooser search, too!), perhaps in some > qt-overlay Documentation/README file or the like, might be considered a bug, > but I'm sure others will be asking it too if they aren't already, and > hopefully with an appropriately keyword searchable bug summary at least some > of them can find this bug/question before they ask it themselves. > > Plus maybe it'll prompt such a readme. =:^) > Some documentation is definitely needed. And afaik there's none at the moment ;) When 4.8.6 enters the tree we might want to release a news item too... although nothing should change for users, at least until the default qtchooser profile points to the qt4 one. Which reminds me that we should write an eselect module to manage the symlink... I'm not a good doc writer, so any help is greatly appreciated in this area.
https://github.com/gentoo/qt/pull/83
Fixed in git.
