On 09/26/2017 03:03 AM, Ian Zimmerman wrote: > On 2017-09-25 22:24, Michael Palimaka wrote: > >> I see a few complaints in this thread, but nobody so far has >> elaborated on the problem they have with this change. > > The problem is that if I want to complete the upgrade the way portage > suggests, I have to (newly) allow in and time-consumingly build _all_ > the qt5 core libraries, since they depend on one another in nearly > circular fashion, and the updated qtcustomplot becomes the "camel's > nose". > > I dealt with this by unmerging the few qt using apps I had installed and > finding alternatives for them. Some of the alternatives are inferior, > but it beats this "eternal transition" qt stuff. I'll make a prediction > but I don't expect anyone to bet: by the time all useful packages > migrate to qt5, the qt6 transition will already be in full swing. >
If the only argument is you don't want to upgrade, I'm afraid there's not much we can do to help you. The reality is that Qt 4 has not been maintained for over 2 years and is starting to break in worse and worse ways. As we do not have the resources to maintain a local fork, we have no choice but to follow upstream's decision to kill it off.
