Summary: | qt5 print support seriously lacking - do NOT remove qt4 support from ebuilds | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Pierre-Yves Bonnetain-Nesterenko <expert-judiciaire> |
Component: | Current packages | Assignee: | Qt Bug Alias <qt> |
Status: | RESOLVED UPSTREAM | ||
Severity: | major | CC: | expert-judiciaire |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Pierre-Yves Bonnetain-Nesterenko
2017-09-26 16:32:40 UTC
You are rather late to notice that, how many Qt4 applications are left at this point where printing is a thing? Unfortunately keeping Qt4 for much longer is not an option, soon it will be impossible to paper over the cracks. Sorry, Qt 4 is completely dead upstream and is breaking worse every day. We don't have the resources to try and keep it on life support. The request was not to ask for maintenance of packages wrt Qt4 (i.e. making patch files to put back Qt4 in some application and the like). It's only not to *delete* Qt4-working ebuilds (masking or keywording them is okay). If some of your workflow depends on proper printing, it is really a pita to have to perform ebuild archeology to get back to previous functionalities - especially if the ebuild dropped Qt4 support without any version change. I do understand that Qt4 is dead and trying to keep it on life support would be sub-optimal. But please do not kill users by deleting ebuild versions we cannot work without (while praying that upstream gets the hint and put things right). (In reply to Pierre-Yves Bonnetain from comment #3) You can't have one: > But please do not kill users by deleting ebuild versions we cannot work > without (while praying that upstream gets the hint and put things right). without the other: > I do understand that Qt4 is dead and trying to keep it on life support would > be sub-optimal. And the correct term to use here isn't 'sub-optimal' but 'impossible'. |