Obsoleted ports hosted on Google Code

[l2dy (Zero King)]

Quoting mojca:

We should not be using google code for anything but obsolete software that is no longer maintained. Disabling the livecheck as a quick fix will just hide the problem. Sure, we may disable it eventually, but we certainly need a ticket tracking progress of moving ports away from google code.

List of ports generated in ​https://trac.macports.org/ticket/53457#comment:6.

Status:

• py-argparse removed in [0d458f93a4295b5fec663b1c6cddff90ac02bc43/macports-ports]
• py-pydot moved in [b238feaaca4b1f76eeb7e22f2dfcbda101d12c54/macports-ports]

[ryandesign (Ryan Carsten Schmidt)]

I dislike megatickets that target this many ports. Each port will have to be investigated individually as to whether a new version is available elsewhere and how to update it, so individual tickets are appropriate so they can be closed as they are resolved.

[mojca (Mojca Miklavec)]

Ryan, while I agree that such tickets are a bit annoying, is there at least some way for us to create those tickets automatically and list those tickets here, so that one can still get an overview (see which tickets are crossed and which ones are not)?

It's not fair to ask human beings to open 150 tickets manually (and get all the details right, including maintainers etc.) when they could be doing much more productive work. In particular I don't expect it from l2dy to create such tickets (and in particular not before getting commit rights and rights to modify tickets). And honestly I strongly suspect that 90% of ports will be fixed by a single person anyway.

I added Rainer (for the sake of automating Trac ticket creation if we agree that is wanted). I'm not sure if we really want 150 tickets.

[mf2k (Frank Schima)]

FWIW, I agree with Mojca in that I prefer a single mega ticket over masses of tickets. Keeping a table of the progress in the description seems to work well too. For me, I already get 100 emails a day for Macports, getting a few more does not change anything.