On 2017-09-26 22:01, Michael Palimaka wrote: > If the only argument is you don't want to upgrade, I'm afraid there's > not much we can do to help you.
You're right that I don't want to upgrade, and I have already explained my workaround for that. But that is _not_ what I'm complaining about in this thread. Rather, my complaint is that such a major change is hidden in an ebuild edit with no version/revision bump, which means I cannot use the normal means (ie. package.mask) to prevent it. Before I decided to drop Qt completely, I had to make a local package of qtcustomplot in my own repo. Surely there are other reasons against this kind of thing? What if someone reports a bug in the package? Now you don't know from the version/rev number if it's linked with Qt4 or Qt5. Is that not important? -- Please don't Cc: me privately on mailing lists and Usenet, if you also post the followup to the list or newsgroup. Do obvious transformation on domain to reply privately _only_ on Usenet.
