#37827: Orphaned dependents from py-matplotlib update ----------------------------+-------------------------------- Reporter: jmr@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: | Keywords: Port: py-matplotlib | ----------------------------+-------------------------------- Comment (by jmr@…): Replying to [comment:2 robitaille@…]:
In the long term, how long do we envisage maintaining Python 2.4 and 2.5 and associated ports? For the modules, I'd generally just remove the old python versions when upstream (the module's) drops support for them. (Though making sure to take care of dependents first, so this kind of ticket doesn't happen.) Where that hasn't happened, it shouldn't be much of a maintenance burden if the unified portgroup is used.
Last time we suggested dropping python24, some users still needed it. We should probably ask again in the not too distant future, since it's no longer getting security updates, and if nobody needs it we're better off getting rid of it so nobody accidentally uses an exploitable version. That should again happen from the top down, deleting dependents or moving them to a newer python version before deleting their dependencies.
Is there a way to find out how many users are actually making use of these? We could probably analyse the logs from packages.macports.org. Though that only tells you how many have been downloaded in any given period, not how many users have them installed. (It's also geographically biased.)
-- Ticket URL: <https://trac.macports.org/ticket/37827#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS