User talk:F1r31c3r

Greetings from maffblaster!
'Hoy F1r31c3r,

I'm glad to see you are making bold moves to improve the Wiki. The memory mapping article was especially interesting. In case you need any assistance please contact me on via Freenode IRC (if you use it) or leave a on my user discussion page. I will usually be able to respond in a relatively short amount of time. This weekend I'll be gone though...

Happy improvements! 

--Maffblaster (talk) 23:25, 11 November 2016 (UTC)

Qt conflicts
So how do you resolve the conflicting issues of a currently installed version of QT?
 * What conflicting issues? — kensington 12:32, 27 October 2015 (UTC)

Issues like QT5 can not be installed at the same time as QT4 and so on. Some QT packages will not accept or be marked for upgrade by portage. You have to remove the old version before emerging the newer version. The old versions can be dependant on other packages which mean they will not be automatically removed. You have to chase these down and remove the offending application bound to the qt package one by one to get the new version of QT to allowed to upgrade. Furthermore packages that only work with QT4 conflicting packages wont be able to work with the new QT5 yet so you have to pick these up with You can then remove the offending packages and keyword it then re-install them against the new qt5 packages once you get them installed.

By removing all old QT4 packages you can see which packages needed them and once you have built qt5 you can re-install these other applications against the new qt5 and avoiding particular package blocks. f1r31c3r
 * Qt5 can most definitely be installed at the same time as Qt4. — kensington 12:57, 27 October 2015 (UTC)

Yes i know but portage wont allow the upgrade or to allow particular QT packages to upgrade while the old qt packages are still installed. Portage will not automatically place all packages into a new slot. I'll take a screen shot later to show you the emerge output. Don't get me wrong, you could just remove each offending QT package one by one or make a script to only remove the offending packages but not everyone can do that so it is easier to just remove all of them and re-install them all with the QT @sets and @preserved-rebuild. It is not ideal but it works. f1r31c3r
 * I can only guess as to the problem without seeing any error output, but perhaps your issue would be solved by updating all Qt packages together eg. via

Yes that is fine when moving from qt5.4 to 5.5 provided you do not have any qt4 packages that are dependent on kde4 packages. f1r31c3r
 * I don't understand. Qt4 and Qt5 are completely coinstallable. — kensington 13:37, 27 October 2015 (UTC)