qt5-qtenginio is obsolete

[Fielding, Eric J (329A)]

It is confusing for people like me who use MacPorts at a more casual level than active developers get a message that “qt5-qtenginio” port should be removed and then to have to figure out how to remove it without breaking other ports we have installed, even if they are inactive.

In fact, I still have a remaining broken port message that I don’t know how to solve:
--->  Scanning binaries for linking errors
--->  Found 1 broken file, matching files to ports
--->  Found 1 broken port:
     py27-pyqt5 @5.8.2
         /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/PyQt5/Enginio.so

Do I just need to delete that one file that appears to be from qt5-qtenginio, but was not removed when I uninstalled it? Or do I need to uninstall and reinstall py27-pyqt5?

Thanks,
	++Eric

-----Original Message-----
From: Clemens Lang <cal at macports.org>
Date: Friday, April 21, 2017 at 3:13 AM

    Hi,
    
    ----- On 21 Apr, 2017, at 00:34, Ryan Schmidt ryandesign at macports.org wrote:
    
    > Are you sure? It doesn't sound like a bug... if qt5 @5.6.2 requires
    > qt5-qtenginio, then isn't it proper for MacPorts to complain when trying to
    > uninstall qt5-qtenginio if qt5 @5.6.2 is still installed
    
    In general yes. However, this message happens for all users that upgrade qt5
    to 5.7.x and requires users to manually uninstall qt5-qtenginio. It would be
    preferable to find an automatic solution for the problem that does not require
    users to manually intervene.
    
    All our deactivate hacks disable dependencies that are still in use by other
    ports.
    
    -- 
    Clemens Lang