| 1 |
Just for fun: |
| 2 |
Open /usr/bin/emerge in a text editor and read the first 10 lines. |
| 3 |
Then run |
| 4 |
grep python-exec /usr/bin/* |
| 5 |
|
| 6 |
It basically is the same what qtchooser does: Forward a python script to |
| 7 |
the appropriate python version. |
| 8 |
|
| 9 |
2018-07-23 13:20 GMT+03:00 Franz Fellner <alpine.art.de@×××××.com>: |
| 10 |
|
| 11 |
> IMO the problem is that qtchooser acts as one point to select ALL |
| 12 |
> components for the default Qt, be it qt4 or qt5 (and possibly qt6 in 2020), |
| 13 |
> without checking if the tool really exists. |
| 14 |
> It just forwards the call to an execuatble with the same name inside the |
| 15 |
> qt-installation's bin dir. (/usr/lib/qt...) |
| 16 |
> qtconfig got removed and people (with DEs lacking qt integration) couldn't |
| 17 |
> configure their fonts/colors/widget style/... anymore. So someone just |
| 18 |
> started to develop a third-party config tool to fill the gap. |
| 19 |
> qtchooser on the other hand is an official qt tool (at least it is hosted |
| 20 |
> on qt's servers). I think that's why they don't just call qt5ct ;) And it |
| 21 |
> would introduce a speacial case for just this one tool. |
| 22 |
> |
| 23 |
> |
| 24 |
> 2018-07-23 13:05 GMT+03:00 Mick <michaelkintzios@×××××.com>: |
| 25 |
> |
| 26 |
>> On Monday, 23 July 2018 10:09:38 BST Franz Fellner wrote: |
| 27 |
>> > Yeah, stupid qtchooser ;) |
| 28 |
>> > |
| 29 |
>> > qtconfig got dropped, use x11-misc/qt5ct instead. |
| 30 |
>> |
| 31 |
>> Thanks Franz, qtconfig used to be installed by default with Qt. I wonder |
| 32 |
>> why |
| 33 |
>> x11-misc/qt5ct isn't treated the same, especially as qtconfig is left on |
| 34 |
>> the |
| 35 |
>> box and is symlinked to qtchooser now. :-/ |
| 36 |
>> |
| 37 |
>> -- |
| 38 |
>> Regards, |
| 39 |
>> Mick |
| 40 |
> |
| 41 |
> |
| 42 |
> |
Archives