> > The problem is: somebody needs to do the correct work to update each of those > ports to the latest version. In many cases, tickets are already filed, and > you can look them up to see what the current status is; if you don't find a > ticket, please file a new one.
Couple of points here. The current "port update" ticket queue I find to be a rather unpredictable mixture of requests of port updates, requests for new ports, announcements that somebody has noticed a version update has come available, and finished port updates awaiting approval by committers. I don’t mind picking off a few of these and updating them, or building some new ones, but it’s a bit of a tangle sometimes. Like this ticket: https://trac.macports.org/ticket/52538 I think this ticket represents someone noticing there’s a new version available, and requesting the existing port be updated. But that should be in a different lineup, IMHO. And there are "requests for ports" ( I think this means new requests for ports that don’t presently exist, mostly) that go back 11 years. Port submissions that go back the same length of time. Possibly some kind of massive clean-out of the old, dead, never-will-be-touched stuff might need to happen. Might be more streamlined and efficient if that all could be aligned better. $0.02. K _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
