#17041: port livecheck makes faulty version comparison ----------------------------------+----------------------------------------- Reporter: devans@macports.org | Owner: macports-tickets@lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: MacPorts base bugs Component: base | Version: 1.7.0 Resolution: | Keywords: livecheck Port: | ----------------------------------+----------------------------------------- Comment(by devans@macports.org): Yes, I agree that when this happens, it is largely due to an inappropriate choice of livecheck source/parameters/whatever and in light of these comments I see that I was responding to the inappropriateness of the conclusion expressed (looks like port is updated). My is that if the latest version from the livecheck source and current version are not equal then there are (at least) two possible causes. One is that the port needs updating but the other is that its the livecheck source/regex that is not up to date, incorrect and this should be reported appropriately. "Somethings wrong with your livecheck." I don't know how to do this without using a version comparison rather than an equality check. Agreed that there aren't enough good livecheck defaults built in. Particularly fresh-meat isn't very good as a last ditch effort as they are frequently not up to date. Maybe have a default livecheck for a site that is not in a list of know sources is not a good idea. In this case, perhaps lint should complain that you don't have a valid livecheck. The more often port has a appropriate livecheck definition included then the less often this sort of problem will occur. -- Ticket URL: <http://trac.macports.org/ticket/17041#comment:8> MacPorts <http://www.macports.org/> Ports system for Mac OS